1
edit
TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Sheriffing/Workflow (view source)
Revision as of 16:22, 23 March 2022
, 23 March 2022Added a Special Cases section in the workflow document with an initial example
Bacasandrei (talk | contribs) (→Filing a regression bug: Added notes to this subsection) |
Alex Finder (talk | contribs) (Added a Special Cases section in the workflow document with an initial example) |
||
| Line 288: | Line 288: | ||
<br /> | <br /> | ||
You can follow up on all the [[TestEngineering/Performance/FAQ#How_do_I_follow_up_on_already_open_regressions_open_by_me.3F|open regression bugs created by you]]. | You can follow up on all the [[TestEngineering/Performance/FAQ#How_do_I_follow_up_on_already_open_regressions_open_by_me.3F|open regression bugs created by you]]. | ||
<br/><br/> | |||
= Special Cases = | |||
== Multiple Bug IDs on the same push == | |||
If the push that has been identified as the culprit has multiple revisions and bug ids linked to it, the sheriff can fill in the "Regressed By" field for each of the bugs with the value of the filed bug for the associated alert. <br/> | |||
TODO: add screenshot for example [https://treeherder.mozilla.org/jobs?repo=autoland&revision=88a481adf83070d1cdcc2bb074f6545b5dfe97e7&group_state=expanded&selectedTaskRun=GAP1DzYETPawhJhP1WkzGw.0/ alert] | |||
= Resources = | = Resources = | ||
* [https://wiki.mozilla.org/TestEngineering/Performance/FAQ FAQ] | * [https://wiki.mozilla.org/TestEngineering/Performance/FAQ FAQ] | ||