Closed
Bug 1270547
Opened 10 years ago
Closed 10 years ago
Add SUBPROCESS_SHUTDOWN_KILL to the crash aggregates
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: benjamin, Assigned: mdoglio)
References
Details
Attachments
(2 files, 1 obsolete file)
In bug 1269961 we added a SUBPROCESS_SHUTDOWN_KILL histogram so that we can measure shutdown-kill crashes separately from others. We need to add this to the aggregates.
|
Reporter | |
Comment 1•10 years ago
|
||
We decided to go with SUBPROCESS_KILL_HARD in bug 1269961 instead, with the reason stored in a keyed histogram. So this patch will need to be updated to handle that. I'm guessing we only want to aggregate on the ShutDownKill reason. Sorry to make this more complicated.
Flags: needinfo?(benjamin)
|
|
Reporter | |
Updated•10 years ago
|
Attachment #8749291 -
Attachment is obsolete: true
Flags: needinfo?(benjamin)
Attachment #8749291 -
Flags: review?(rvitillo)
|
|
Reporter | |
Comment 3•10 years ago
|
||
|
|
Reporter | |
Updated•10 years ago
|
Attachment #8749697 -
Flags: review?(rvitillo)
|
||
Updated•10 years ago
|
Attachment #8749697 -
Flags: review?(rvitillo) → review+
|
|
||
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
|
|
||
Comment 4•10 years ago
|
||
Reopening this as the code has to be ported to the Scala version as well, which Mauro is planning to deploy asap.
|
|
||
Updated•10 years ago
|
Assignee: benjamin → mdoglio
|
|
Reporter | |
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
|
|
Assignee | |
Comment 6•10 years ago
|
||
Attachment #8751209 -
Flags: review?(rvitillo)
|
|
||
Updated•10 years ago
|
Attachment #8751209 -
Flags: review?(rvitillo) → review+
|
|
||
Updated•10 years ago
|
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
|
||
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•