We released Firefox for Android beta 6 yesterday. Using the super search I am unable to get a current overview of the crash data. The advanced search would update once an hour seems like super search indexes once a day? My super search url https://crash-stats.mozilla.com/search/?product=FennecAndroid&version=35.0b6&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform The advanced search url that returns results https://crash-stats.mozilla.com/query/?product=FennecAndroid&version=FennecAndroid%3A35.0b6&range_value=1&range_unit=weeks&date=12%2F24%2F2014+15%3A00%3A00&query_search=signature&query_type=contains&query=&reason=&release_channels=&build_id=&process_type=any&hang_type=any Note that these urls will eventually work, just iterate to the current beta normally released on Wednesday.
Super Search actually is usually displaying even newer data than advanced search. Super Search has data that is submitted, while Advanced Search was 1-2h behind.
What might not work correctly is the "b6" part.
As KaiRo guessed, the problem here comes from the version number. If you want to see results for a specific build, you need to use the build id filter instead. For example: https://crash-stats.mozilla.com/search/?product=FennecAndroid&build_id=20141222200017 Marking this as worksform. If the version thing is problematic, please file a new bug for it specifically.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
That is a horrible answer. Requiring the user to find the build ID is a major regression in the functionality between advanced search and super search. Crash-stats builds that URL for me. 1) Choose a current beta ex. https://crash-stats.mozilla.com/topcrasher/products/FennecAndroid/versions/35.0b10?days=7 2) Click the super search button 3) Super search form is pre-filled with FennecAndroid and 35.0b10
@adrian -- I'm confused. Why do these eventually populate but initially fail to return?
This continues to be a thorn in my side.
(In reply to Kevin Brosnan [:kbrosnan] from comment #6) > This continues to be a thorn in my side. And I think that bug 1131068 is better for this, actually, as it describes the actual issue behind what you have seen here.
I will work on a solution for the "beta" problem in bug 1000160. I'm not sure I understand this statement though: > Note that these urls will eventually work, just iterate to the current beta normally released on Wednesday. Does that mean that results will start showing up after some time, without changing anything to the URL / form? If that's the case, I'd love to see a reproducible case, with for example some uuids.
I had used a beta version we had just built but not released so the data was not populated at the time of comment 0.
Adrian, https://bugzilla.mozilla.org/show_bug.cgi?id=1000160 is now resolved. Does that resolve the problem Kevin is having?
Yes, beta version numbers are now inserted in the json documents directly, so they are supported in Super Search.
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago → 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.