Closed
Bug 1594247
Opened 6 years ago
Closed 6 years ago
Do not automatically set the severity of crashes to `critical`
Categories
(Tree Management :: Treeherder, defect)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emceeaich, Unassigned)
References
Details
Attachments
(1 file)
Not all crashes are the same. Some are transient. Some are caused by the test environment. Others affect a small number of users.
Marking every crash as severity = critical creates a noisy signal.
Treeherder already marks crash bugs with the crash keyword.
We would prefer that either:
- A non-default severity is never set when creating a crash bug
- If a crash exceeds some threshold set in Treeherder (users, frequency, etc) then the crash bug is set with
criticalseverity.
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Attachment #9107174 -
Flags: review?(cdawson)
Updated•6 years ago
|
Attachment #9107174 -
Flags: review?(cdawson) → review+
Comment 2•6 years ago
|
||
This is merged.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•