342
edits
TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions
TestEngineering/Performance/Sheriffing/Workflow (view source)
Revision as of 11:36, 29 March 2022
, 29 March 2022→Context
Alexandrui (talk | contribs) |
Alexandrui (talk | contribs) |
||
| Line 2: | Line 2: | ||
Performance sheriffs, along with the standard [[TestEngineering/Performance/Sheriffing#Overview|by-the-book definition]], are responsible for checking for performance regressions on a daily basis. This is done by reviewing alerts from our performance tests on [https://treeherder.mozilla.org/perf.html Perfherder]. Any time a test or tests exceed [[TestEngineering/Performance/Sheriffing/Workflow#Thresholds|the set threshold for its framework]], one or multiple alerts will be generated. The goal of the sheriff is to identify the commit or revision responsible for the regression, and file a bug with a :needinfo flag for the author(s) of that commit or revision. | Performance sheriffs, along with the standard [[TestEngineering/Performance/Sheriffing#Overview|by-the-book definition]], are responsible for checking for performance regressions on a daily basis. This is done by reviewing alerts from our performance tests on [https://treeherder.mozilla.org/perf.html Perfherder]. Any time a test or tests exceed [[TestEngineering/Performance/Sheriffing/Workflow#Thresholds|the set threshold for its framework]], one or multiple alerts will be generated. The goal of the sheriff is to identify the commit or revision responsible for the regression, and file a bug with a :needinfo flag for the author(s) of that commit or revision. | ||
= Flowchart = | |||
[[File:Sheriffing workflow v3.png|left|Sheriffing workflow]]<br/> | [[File:Sheriffing workflow v3.png|left|Sheriffing workflow]]<br/> | ||
[[File:Workflow followup.png|left|Workflow followup]]<br/><br/> | [[File:Workflow followup.png|left|Workflow followup]]<br/><br/> | ||