Canmove, confirm
2,850
edits
Changes
→Classifying/Starring jobs
That's it! You've classified/starred a job! You can move on to a different failed job.
== Starring many failures at once ==
Sometimes things go seriously wrong in CI, e.g.:
* developer lands bad code
* a broken dependency is introduced
* a system configuration change goes awry
This manifests as lots on concurrent failures displayed in Treeherder. Luckily, Treeherder allows you to pin up to 500 jobs at one time, greatly speeding up the starring process.
If the failure is pervasive, i.e. platform-independent, you can use Treeherder to show unclassified failures. Pin all the failures for a single push, and then mark them as "fixed by commit." so repeat until it's done for that single push, then move on to the next push.
If only a subset of platforms are affected, i.e. all on one build target or test suites, you can filter on the top right of the Treeherder interface with the search field and also filter for the job name (substring) which is shown at the bottom left if you select a job
If the failure doesn't affect all test jobs of one test suite on the same platform and build target, you will need to manually go through the list and add them to the pinboard before marking them as "fixed by commit." This reduces the likelihood of mis-starring.
If it's an older regression which has been resolved many pushes ago, selecting and starring all these test failures as "fixed by commit" might outweigh the time needed to do it manually. Other regressions should have been caught by the later pushes after the backout of the obvious test failure.
= More Treeherder Resources =
More information about the Treeherder project can be found [[Auto-tools/Projects/Treeherder|here]].
