Confirmed users
571
edits
Sheriffing/How To/Intermittent bugs: Difference between revisions
Sheriffing/How To/Intermittent bugs (view source)
Revision as of 11:16, 21 October 2019
, 21 October 2019→Machine-specific failures: added termination/quarantine instructions
(add info about Test-Verify: how to find the original test suite) |
(→Machine-specific failures: added termination/quarantine instructions) |
||
| Line 102: | Line 102: | ||
[[File:Sheriffing intermittent failures dead pixel.png|reftest analyzer with highlighted dead pixel outside of area with content created for testing]] | [[File:Sheriffing intermittent failures dead pixel.png|reftest analyzer with highlighted dead pixel outside of area with content created for testing]] | ||
Terminate the machine if you discover such an issue. | Terminate the machine if you discover such an issue: | ||
# In Treeherder with the job selected, click the link '''Task: <something>''' at the bottom left. | |||
# Click on the tab '''Task Run 0 (Latest)'''. If the number is not <code>0</code>, the job ran multiple times. Find the one in Treeherder by comparing the '''Job Ended''' time in Treeherder (bottom left) with the line Resolved in Taskcluster. Move the mouse over it to see the timestamp. | |||
# Click on '''WorkerId'''. | |||
* If there are many failed jobs listed for that machine, terminate it if it's rented one or quarantine it if it's owned by Mozilla (termination button not offered in that case). | |||
* If in doubt, terminate it. | |||
* If you quarantine a machine, let #ci on IRC know. | |||
== How to file a security bug == | == How to file a security bug == | ||