160
edits
TestEngineering/Performance/Sheriffing: Difference between revisions
TestEngineering/Performance/Sheriffing (view source)
Revision as of 12:55, 15 January 2018
, 15 January 2018title case
(e10s is always on now) |
(title case) |
||
| Line 47: | Line 47: | ||
== Determining if we have all the data from Treeherder == | == Determining if we have all the data from Treeherder == | ||
Since an alert is a suggestion of the original changeset, I always open the graph view, zoom in to a narrow window, then open the test job (from the link shown when clicking on a data point) of a job in the future. Then I filter the | Since an alert is a suggestion of the original changeset, I always open the graph view, zoom in to a narrow window, then open the test job (from the link shown when clicking on a data point) of a job in the future. Then I filter the Treeherder view down and show the next 10 jobs. This gives you a range of pushes to see coalescing, retriggers, and allows you to fill in the holes by retriggering and scheduling jobs. | ||
Here we are looking for a few things: | Here we are looking for a few things: | ||
* Do we have data for the revision before / after the revision we have identified as regressing? If not, we should consider filling in the missing data. | * Do we have data for the revision before / after the revision we have identified as regressing? If not, we should consider filling in the missing data. | ||