342
edits
TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions
TestEngineering/Performance/Sheriffing/Workflow (view source)
Revision as of 08:22, 6 November 2023
, 6 November 2023→Handling alerts
Alexandrui (talk | contribs) |
Alexandrui (talk | contribs) |
||
| Line 114: | Line 114: | ||
When an alert is created, it is not necessarily caused by a bug. It can be also caused by the instability/noise of the test or by other causes that are unrelated to the repo code, like CI setup. | When an alert is created, it is not necessarily caused by a bug. It can be also caused by the instability/noise of the test or by other causes that are unrelated to the repo code, like CI setup. | ||
<br /> | <br /> | ||
<br /> | |||
A bug associated with an alert needs to have the perf-alert keyword. The regression bugs have that automatically when the File bug button is pressed, but for the bugs that are not regression bugs needs to be added manually. | |||
== Thresholds == | == Thresholds == | ||
There are different thresholds above which the alerts are considered regressions and they vary depending on the framework: | There are different thresholds above which the alerts are considered regressions and they vary depending on the framework: | ||