Confirmed users
3,376
edits
(→choosing a config to test: format) |
m (→choosing a starting point: initial data) |
||
Line 11: | Line 11: | ||
= choosing a starting point = | = choosing a starting point = | ||
Ideally you want to pick the first instance of a failure and work backwards in time to find the root cause. | |||
In practice this can be confusing as we have multiple branches or sometimes different configs that fail at different times. | |||
I would look at the first 10 failures and weigh: | |||
* what branch is most common | |||
* where do the timestamps end up close to each other | |||
* is the most common config on the same branch and with close timestamps | |||
In many cases you will pick a different failure as the first point- I often like to pick the second instance of the branch/config so I can confirm multiple revisions show the failure (show a pattern). | |||
= how to find which job to retrigger = | = how to find which job to retrigger = | ||
= how many retriggers = | = how many retriggers = | ||
= what to do with the data = | = what to do with the data = | ||
= exceptions = | = exceptions = |