Confirmed users
3,376
edits
Auto-tools/Projects/Stockwell/backfill-retrigger: Difference between revisions
Jump to navigation
Jump to search
m
Auto-tools/Projects/Stockwell/backfill-retrigger (view source)
Revision as of 16:57, 14 March 2018
, 14 March 2018→choosing a config to test: - first draft
(add data as headers) |
m (→choosing a config to test: - first draft) |
||
| Line 1: | Line 1: | ||
= finding bugs to work on = | = finding bugs to work on = | ||
= choosing a config to test = | = choosing a config to test = | ||
It is best to look at the existing pattern of data you see when looking at all the starred instances. Typically when adding a comment to a bug while triaging it is normal to list the configurations that the failures are most frequent on. Usually pick the most frequency configuration, maybe if it is a tie for 2 choose both of those. | |||
If there is not a clear winner, then consider a few factors which could help: | |||
1) debug typically provides more data, but takes longer | |||
2) pgo is harder to backfill and builds take longer- try to avoid this | |||
3) ccov/jsdcov builds/tests are only run on mozilla-central- avoid these configs | |||
4) nightly is only run on mozilla-central- avoid these configs | |||
5) mac osx has a limited device pool- try to pick linux or windows | |||
= choosing a starting point = | = choosing a starting point = | ||
= how to find which job to retrigger = | = how to find which job to retrigger = | ||