15
edits
TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Sheriffing/Workflow (view source)
Revision as of 14:55, 23 February 2024
, 23 February 2024→Regression which was already backedout
Bacasandrei (talk | contribs) (→Alert caused by a backout: Adding description.) |
Bacasandrei (talk | contribs) |
||
| Line 439: | Line 439: | ||
In this case we reply to the backout comment with the summary of the alert and adding the ''perf-alert'' keyword. | In this case we reply to the backout comment with the summary of the alert and adding the ''perf-alert'' keyword. | ||
== Regression | == Regression which was already backedout == | ||
If we identify a regression alert summary and that particular changeset was already backout then the safe approach would be to file a bug by following the usual workflow, but mention in the comment0 that this was already backedout and there's no action item for the author. This bug is only created for tracking purposes / being able to acknowledge the change summary of the alert. | |||
= Resources = | = Resources = | ||
* [https://wiki.mozilla.org/TestEngineering/Performance/FAQ FAQ] | * [https://wiki.mozilla.org/TestEngineering/Performance/FAQ FAQ] | ||