No distinction between *just* crash problems vs. the whole set

Bug #1043426 reported by Evan
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Errors
Fix Released
Undecided
Unassigned

Bug Description

Once we start collecting reports for RecoverableProblem, Hang, Package, KernelOops, and other ProblemTypes, we should ensure that we continue to track the average errors per day for Ubuntu 12.10 and future releases with *just* the Crash ProblemType. This will let us compare like-for-like against Ubuntu 12.04, which only had the Crash ProblemType.

Obviously we should also maintain a line for *all* types of problems.

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

This is a special case of the general problem, "show me errors, in version Y, of types that were also captured in version X".

For a particularly thorny example, imagine that Ubuntu 12.10 reports hangs of 30 seconds or longer, while Ubuntu 13.04 ratchets that down to 10 seconds or longer. On the graph, hangs of over 30 seconds should show up on the "13.04 by 12.10 standards" line, while hangs of between 10 and 30 seconds should not.

summary: - When we start pulling in more problem types, continue to track *just*
- crash problems in addition to the whole set
+ No distinction between *just* crash problems vs. the whole set
Changed in errors:
status: New → In Progress
Revision history for this message
Evan (ev) wrote :

This is fixed in production. We now have a separate line for "by 12.04 standards." Matthew, you mentioned that we need some way of tracking the usage of recoverable errors, as we don't want its usage growth among developers to add noise to the graph. I've filed bug 1084079 for that.

Changed in errors:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.