canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,714
edits
TestEngineering/Performance/Triage Process: Difference between revisions
TestEngineering/Performance/Triage Process (view source)
Revision as of 12:51, 12 February 2020
, 12 February 2020More info about crash handling
(Define priority for important intermittent failures) |
(More info about crash handling) |
||
| Line 17: | Line 17: | ||
* P4 - Not used (reserved for bots) | * P4 - Not used (reserved for bots) | ||
* P5 - Used for intermittent failures, or no intention to fix but will accept patches | * P5 - Used for intermittent failures, or no intention to fix but will accept patches | ||
== FAQ == | |||
=== How to handle intermittent bugs which cover a crash of Firefox? | |||
First make sure it doesn't stay in the Testing component but gets moved to a product that covers Firefox. Therefore check the crashing thread and find the first stack which is part of our code. Search for the associated file name in searchfox, and find the corresponding Bugzilla component within the nearest moz.build file. If not done yet, also add a comment with the link to the exact crash location. Make sure to keep the changeset id in the URL. | |||