Confirmed users
571
edits
Sheriffing/How To/Intermittent bugs: Difference between revisions
Jump to navigation
Jump to search
m
made intro less ambiguous
m (cleaned up bugfiler section) |
m (made intro less ambiguous) |
||
| Line 1: | Line 1: | ||
{{Sheriffing How To|Intermittent bugs}} | {{Sheriffing How To|Intermittent bugs}} | ||
When you find a test that fails | When you find a test that fails sometimes, you've hit an intermittent failure. This is the most annoying class of failures for both sheriffs and developers because it is not necessarily related to the code under test, but more likely indicates that the test itself might need to change to improve stability. | ||
The test failure may have happened before and a bug may already be on file. In such cases, Treeherder should suggest the bug number and title under the failure, e.g.: | The test failure may have happened before and a bug may already be on file. In such cases, Treeherder should suggest the bug number and title under the failure, e.g.: | ||