15
edits
TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions
TestEngineering/Performance/Sheriffing/Workflow (view source)
Revision as of 12:33, 10 July 2024
, 10 July 2024→Alert caused by a backout: removed section because we added the details elsewhere
Bacasandrei (talk | contribs) (→Backout/regression-fix alerts: update explanation) |
Bacasandrei (talk | contribs) (→Alert caused by a backout: removed section because we added the details elsewhere) |
||
| Line 442: | Line 442: | ||
# '''''decision''''' alerts usually are just spikes and not relevant, which is why we are setting them as ''invalid''. In the case that, by looking at the coresponding graph, the regression wasn't improved / fixed, then check with the other sheriffs in the Sheriffs of Performance channel on Element since it might be a cause of concern. | # '''''decision''''' alerts usually are just spikes and not relevant, which is why we are setting them as ''invalid''. In the case that, by looking at the coresponding graph, the regression wasn't improved / fixed, then check with the other sheriffs in the Sheriffs of Performance channel on Element since it might be a cause of concern. | ||
# '''''instrumented''''' in the Tags & Options column should be set as ''invalid''. Alerting will be deactivated for these tests in the future. | # '''''instrumented''''' in the Tags & Options column should be set as ''invalid''. Alerting will be deactivated for these tests in the future. | ||
== Regression which was already backedout == | == Regression which was already backedout == | ||