Closed Bug 706687 Opened 13 years ago Closed 7 years ago

Flip logic for painting/listing crash rates so "no crashes but ADUs" results in a 0 value

Categories

(Socorro :: Webapp, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: kairo, Unassigned)

Details

Some of the confusion in bug 663432 and other cases (even caught myself at times) is that on the front page graph and in /daily we are painting no value (and displaying "-" for all columns) when we have no crashes but we have ADUs. OTOH, we are painting zero values when we have crashes but no ADUs, i.e. the "division by zero" case. We should flip this around and instead paint a 0 value when we have no crashes but non-zero ADUs, and not paint anything when we have zero ADUs. When either of the values is non-zero, we should always least list this fact in the table in /daily, though. I guess displaying "-" when we have no value for this item is OK, but in the case where we have ADUs but no crashes, it might even looks better to have a "0" in the crashes column.
Component: Socorro → General
Product: Webtools → Socorro
Component: General → Webapp
Laura, it would be nice if we could get that into a release, I guess it's not a lot of work.
Assignee: nobody → rhelmer
Status: NEW → ASSIGNED
Not actively working on this, easier now that we have the django app only to deal with.
Assignee: rhelmer → nobody
we have changed frameworks and graphing libs and this may not be a problem. even if it is still present, we intend to migrate to data platform for investigations of rates.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.