Closed Bug 558683 Opened 10 years ago Closed 9 years ago
Socorro UI - inconsistent date ranges in TCBS report
Bug 534443 addressed the issue of aggregating only the current day's data for the Nightlies. Unfortunately, the UI is going to have to follow suit in treating the nightlies differently. When going to the TCBS report, the default interval is two weeks. For nightlies, it is likely best to be just 24 hours. That way the devs can see only what is the top crash in the current nightly version. The TCBS report allows different date ranges based on 3, 7, 14 or 28 days. Adding a 1 day and making it the default for nightlies would probably be best. Also when clicking on a signature in one of from a report tagged as 3, 7, or 28 days returns a report with a 14 day range. These ranges should be synchronized.
Moving onto the 1.7.8 milestone.
Target Milestone: --- → 1.7.8
it looks like the problem that I mentioned in the last paragraph has been fixed sometime in the last year since the bug was filed. The situation was when clicking on a signature in a 3, 7, or 28 day report, you'd get a page of crashes. If you examined the url, the "range_value" would always be 14 without regard to the previously selected range. I now see the proper value in the "range_value".
Attachment #528921 - Flags: review?(rhelmer) → review+
Fixed in revision 3119.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Verified FIXED on https://crash-stats-dev.allizom.org/topcrasher/byversion/Firefox/5.0/1/browser: Top 181 Crashing Signatures. 2011-05-17 11:00:00 through 2011-05-18 11:00:00. The report covers 100.00% of all 379 crashes during this period. Graphs below are dual-axis, having Count (Number of Crashes) on the left X axis and Percent of total of Crashes on the right X axis. Spot-checked a few incident to ensure their "Date Processed" timestamp was within the 1-day range.
Status: RESOLVED → VERIFIED
OS: Mac OS X → All
Hardware: x86 → All
Component: Socorro → General
Product: Webtools → Socorro
Component: General → Webapp
You need to log in before you can comment on or make changes to this bug.