15
edits
TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Sheriffing/Workflow (view source)
Revision as of 15:04, 23 February 2024
, 23 February 2024→Special Cases: Jobs failing to run description
Bacasandrei (talk | contribs) |
Bacasandrei (talk | contribs) (→Special Cases: Jobs failing to run description) |
||
| Line 441: | Line 441: | ||
== Regression which was already backedout == | == 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. | 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. | ||
== Jobs are failing to run == | |||
In this case we usually resort to bisection. | |||
= Resources = | = Resources = | ||
* [https://wiki.mozilla.org/TestEngineering/Performance/FAQ FAQ] | * [https://wiki.mozilla.org/TestEngineering/Performance/FAQ FAQ] | ||