15
edits
TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Sheriffing/Workflow (view source)
Revision as of 12:50, 23 February 2024
, 23 February 2024→Multiple Bug IDs on the same push
Bacasandrei (talk | contribs) (→How to Become a Sheriff: Corrected mistake) |
Bacasandrei (talk | contribs) |
||
| Line 376: | Line 376: | ||
= Special Cases = | = Special Cases = | ||
== Multiple Bug IDs on the same push == | == Multiple Bug IDs on the same push == | ||
=== Regressions === | |||
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/> | 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/> | ||
If there's a regression-fix, regression-backedout or improvement-backedout bug to be linked to the alert but the revision contains multiple bugs, link the most relevant bug to the alert. If you're unsure, ni? the author to tell which of the bugs they think caused the alert. | If there's a regression-fix, regression-backedout or improvement-backedout bug to be linked to the alert but the revision contains multiple bugs, link the most relevant bug to the alert. If you're unsure, ni? the author to tell which of the bugs they think caused the alert. | ||
=== Improvements === | |||
The general approach for improvements is to leave needinfos to the authors to ask for help in identifiying the corresponding bug. | |||
== Sheriffing Firefox-Android Alerts == | == Sheriffing Firefox-Android Alerts == | ||