Confirmed users
1,052
edits
User:RyanVM/Job Visibility Policy Updates: Difference between revisions
Jump to navigation
Jump to search
User:RyanVM/Job Visibility Policy Updates (view source)
Revision as of 13:47, 6 July 2015
, 6 July 2015wording tweaks
No edit summary |
(wording tweaks) |
||
| Line 19: | Line 19: | ||
* Full logs should be available for both successful and failed runs in either raw or structured formats. | * Full logs should be available for both successful and failed runs in either raw or structured formats. | ||
* 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 | * 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/log_parser/utils.py bug suggestion generator] (otherwise sheriffs have to manually search Bugzilla when classifying/annotation intermittent failures): | * Failure output must be in the format expected by the Treeherder's [https://github.com/mozilla/treeherder-service/blob/master/treeherder/log_parser/utils.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): | ||