342
edits
TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Sheriffing/Workflow (view source)
Revision as of 10:32, 11 March 2022
, 11 March 2022→Harness alerts
Alexandrui (talk | contribs) |
Alexandrui (talk | contribs) |
||
| Line 119: | Line 119: | ||
=== Harness alerts === | === Harness alerts === | ||
Harness alerts are usually caused by re-recordings or changes to code | Harness alerts are usually caused by re-recordings or changes to code from testing/raptor component changing the baseline. If the regression is assumed, then link the culprit directly to the alert, close as wontfix and add the "harness" tag. Otherwise, open regression bug. | ||
=== Backout/regression-fix alerts === | === Backout/regression-fix alerts === | ||