Sheriffing/How To/Intermittent bugs: Difference between revisions

Jump to navigation Jump to search
m
fixed ordering of paragraphs
(add need for retriggering of some mobile failures)
m (fixed ordering of paragraphs)
 
Line 49: Line 49:


There is also a [https://sql.telemetry.mozilla.org/dashboard/permafailing-tests dashboard] to check for permafailing tasks.
There is also a [https://sql.telemetry.mozilla.org/dashboard/permafailing-tests dashboard] to check for permafailing tasks.
= Mobile Failures =
If tasks for mobile products like Firefox for Android failure, they need to retriggered until they succeed or the changeset causing the permanent issue has been backed out if the task group ends with "-debug", "-beta" or "-nightly". Without the successful run, the mobile Nightly does not ship to users.


== Filter Treeherder by test path ==
== Filter Treeherder by test path ==
Line 62: Line 59:
* As filter value, enter the path of the folder which contains the test but without test name. E.g. if you want to find toolkit/components/passwordmgr/test/browser/browser_doorhanger_generated_password.js the search should be for toolkit/components/passwordmgr/test/browser/
* As filter value, enter the path of the folder which contains the test but without test name. E.g. if you want to find toolkit/components/passwordmgr/test/browser/browser_doorhanger_generated_password.js the search should be for toolkit/components/passwordmgr/test/browser/
* Press Enter.
* Press Enter.
= Mobile Failures =
If tasks for mobile products like Firefox for Android failure, they need to retriggered until they succeed or the changeset causing the permanent issue has been backed out if the task group ends with "-debug", "-beta" or "-nightly". Without the successful run, the mobile Nightly does not ship to users.


= General failure messages - deciding if new bug needed =
= General failure messages - deciding if new bug needed =
Confirmed users
571

edits

Navigation menu