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:30, 15 March 2018
, 15 March 2018→finding bugs to work on: initial data
(→how many retriggers: backfilling) |
m (→finding bugs to work on: initial data) |
||
| Line 1: | Line 1: | ||
= finding bugs to work on = | = finding bugs to work on = | ||
We have a [https://charts.mozilla.org/FreshOranges1/index.html fresh oranges dashboard] which looks like neglected oranges, except that it shows new failures that are high frequency and ignoring [stockwell infra] bugs. | |||
As these are new bugs, there will be issues here that are infra or harness related, use this as an opportunity to annotate [stockwell infra] if it is build, taskcluster, network, machine related. Otherwise rules are similar to disable-recommended- if a testcase is in the bugzilla summary, we should be able to retrigger and find the patch which caused this to become so frequent. | |||
= 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. | 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. | ||