canmove, Confirmed users
1,394
edits
Sheriffing/Job Visibility Policy: Difference between revisions
Jump to navigation
Jump to search
→Usable job logs
(Overhaul the policy in light of Tier 2 jobs and other various cleanups) |
|||
| Line 20: | Line 20: | ||
* The crash reporter should be enabled, mini-dumps processed correctly (ie: with symbols available) & the resultant valid crash stack visible in the log (it is recommended to use mozcrash to avoid reinventing the wheel). | * The crash reporter should be enabled, mini-dumps processed correctly (ie: with symbols available) & the resultant valid crash stack visible in the log (it is recommended to use mozcrash to avoid reinventing the wheel). | ||
* Failures must appear in the Treeherder failure summary in order to avoid having to open the full log for every failure. | * Failures must appear in the Treeherder failure summary in order to avoid having to open the full log for every failure. | ||
* Failure output must be in the format expected by the Treeherder's [https://github.com/mozilla/treeherder-service/blob/master/treeherder/ | * Failure output must be in the format expected by the Treeherder's [https://github.com/mozilla/treeherder-service/blob/master/treeherder/model/error_summary.py bug suggestion generator] (otherwise sheriffs have to manually search Bugzilla when classifying/annotation intermittent failures): | ||
** For in-tree/product issues (eg: test failures, crashes): | ** For in-tree/product issues (eg: test failures, crashes): | ||
*** Delimeter: ' | ' | *** Delimeter: ' | ' | ||