1213247 - [staging] No results for plugin crashes for latest Firefox

Status: VERIFIED FIXED

(Socorro :: General, task)

Description

[Dave Hunt [:davehunt] [he/him] ⌚BST]

Our functional tests picked up an issue due to there being no results for plugin crashers against the latest version of Firefox. The failing URL is: https://crash-stats.allizom.org/topcrasher/products/Firefox/versions/43.0a1/date_range_type/report/crash_type/plugin/os_name/None/result_count/50?days=7

I am able to replicate this by visiting the URL. The affected test is https://github.com/mozilla/Socorro-Tests/blob/41f7e32008942f48e4c19b6519acb1e4e5b6243b/tests/test_crash_reports.py#L77

The tests appear to be very dependent on existing data. Is there a way to ensure that staging always has the appropriate data, or for our tests to remotely create the data they need?

Comment 1

[Dave Hunt [:davehunt] [he/him] ⌚BST]

I've opened a pull request to mark this test as expected to fail until this is resolved:
https://github.com/mozilla/Socorro-Tests/pull/329

Comment 2

[Dave Hunt [:davehunt] [he/him] ⌚BST]

This is now fixed and the test is no longer expected to fail. I'm not sure what the fix was, perhaps Matt can provide details?

Comment 3

[Matt Brandt [:mbrandt]]

peterbe, can you confirm what the tweak was that fixed this?

Comment 4

[Matt Brandt [:mbrandt]]

Was the combination of bug 1214436 and bug 1212096 the remedy?

Comment 5

[Peter Bengtsson [:peterbe]]

(In reply to Matt Brandt [:mbrandt] from comment #4)
> Was the combination of bug 1214436 and bug 1212096 the remedy?

Most definitely. At least I think so. 

So Matt, there's now a manual step whereby a superuser can click one button and the stage can get the same featured versions as prod.

Comment 6

[Matt Brandt [:mbrandt]]

Woot-tastic .. bumping to verified.