Reading and interpreting try server Treeherder test runs is not intuitive. This bug is to add documentation on how to know when to rerun tests or how to identify intermittent failures on Treeherder. This bug is to add docs to explain: * Intermittent Failures * Identification and how to prevent (link to this for [prevention](https://mozilla.slack.com/archives/G01EU5QU35Y/p1718735353845329)) * Identifying via existing listed intermittents * How to check Similar Jobs * What a "good" run should look like * How to rerun jobs * How to trigger jobs from Treeherder UI * Anything else that is not intuitive about Treeherder Goal of docs is to: * Explain how to idenitfy a clear or good-to-go try push * Information on how to use Treeherder
Bug 1906741 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Reading and interpreting try server Treeherder test runs is not intuitive. This bug is to add documentation on how to know when to rerun tests or how to identify intermittent failures on Treeherder. This bug is to add docs to explain: * Intermittent Failures * Identification and how to prevent (link to this for [prevention](https://firefox-source-docs.mozilla.org/devtools/tests/debugging-intermittents.html)) * Identifying via existing listed intermittents * How to check Similar Jobs * What a "good" run should look like * How to rerun jobs * How to trigger jobs from Treeherder UI * Anything else that is not intuitive about Treeherder Goal of docs is to: * Explain how to idenitfy a clear or good-to-go try push * Information on how to use Treeherder