Closed Bug 627123 Opened 13 years ago Closed 13 years ago

ADU values for Firefox 3.6.13 not using the default value provided in admin panel

Categories

(Socorro :: General, task)

task
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 628424

People

(Reporter: christian, Assigned: ryansnyder)

Details

The crash stats for 3.6.13 are way too low:

  http://crash-stats.mozilla.com/products/Firefox/versions/3.6.13

Looks like this has been happening for a while:

  http://crash-stats.mozilla.com/daily?p=Firefox&v[]=3.6.13
Might just be those views, looks like there is more volume on http://crash-stats.mozilla.com/topcrasher/byversion/Firefox/3.6.13
Assignee: nobody → laura
Christian, what is the issue exactly?  The number of crashes submitted?  The average number of crashes per user?  Can you give us more specifics about which values are way too low and what you're expecting them to be?
The magnitude of crashes is off. Normally branch releases hover around 2 crashes / ADU. Right now we're at .16 crashes / ADU. That means either we somehow gained a bunch of ADUs without them crashing (unlikely), the crashes aren't being counted/recorded, or there is some throttle funkiness.

Looking at http://crash-stats.mozilla.com/daily?p=Firefox&v[]=3.6.13 the ADUs look sane / in the typical range we see, it's the crashes that look artificially low.

Digging deeper, on http://crash-stats.mozilla.com/daily?p=Firefox&v[]=3.6.13, when I click generate (I guess applying the 10% throttle) everything goes back to looking normal. When I go to the admin side and try to edit 3.6.13 it already says the throttle is 10 though. I can't set the throttle on some views (like http://crash-stats.mozilla.com/products/Firefox/versions/3.6.13) so they are "broken" to me.

I'm bumping this down from a blocker because I think data isn't being lost.
Severity: blocker → critical
Is the throttle set to the right value?  It's currently set to 10% in the admin / branches page as the default value to be used by ADU.  If we bump that to 100% then the value shifts to 1.6 crashes per active daily user.
It should be at 10% (bug 617968).
It's correct at 10% in the collector config, just checked.  Seems like some of the graphs have it at 100% though.
Hm, yeah, it looks like ADU values are being calculated at 100% instead of the default value associated with Firefox 3.6.13 (10%).  Updating ticket title accordingly.
Summary: Firefox 3.6.13 crashes don't look to be recorded → ADU values for Firefox 3.6.13 not using the default value provided in admin panel
Whew, glad we're not losing data :-)
I'll take a look at this for 1.7.7.  We should be able to ship 1.7.7 shortly after the PHX migration.
Assignee: laura → ryan
Severity: critical → major
Status: NEW → ASSIGNED
Target Milestone: --- → 1.7.7
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.