Confirmed users
571
edits
Sheriffing/How To/Intermittent bugs: Difference between revisions
Sheriffing/How To/Intermittent bugs (view source)
Revision as of 16:35, 15 January 2018
, 15 January 2018added dead pixel explanation and example
(Explained that shorted file path might be necessary in search) |
(added dead pixel explanation and example) |
||
| Line 40: | Line 40: | ||
Treeherder syncs with Bugzilla several times a day. Once your bug is added and the systems sync, Treeherder will suggest your new bug as a match for the next intermittent failure of this type. | Treeherder syncs with Bugzilla several times a day. Once your bug is added and the systems sync, Treeherder will suggest your new bug as a match for the next intermittent failure of this type. | ||
== Machine-specific failures | |||
Machines can get into a bad or be in that from the start (e.g. bad memory). This will fall all or just more tests than usual, often in the same test type. | |||
webgl ("gl") and reftests ("R") might fail because of dead pixels which can be far away from any content that gets rendered. In the following zoomed out example, the red rectangle is at the bottom and is a dead pixel which causes the test to fail. | |||
[[File:Sheriffing intermittent failures dead pixel.png|reftest analyzer with highlighted dead pixel outside of area with content created for testing]] | |||