TestEngineering/Performance/RegressionBugsHandling: Difference between revisions

← Older edit

TestEngineering/Performance/RegressionBugsHandling (view source)

Revision as of 13:50, 26 August 2021

1,021 bytes added , 26 August 2021

Updated link to build metrics.

Gsquelart

9

edits

@@ Line 1: / Line 1: @@
 = Handling of Performance Regression Bugs =
+Below you'll find references to information about how you can investigate a potential regression for each framework.
-We use different policies for handling large and small regressions.
+== Raptor regressions ==
+More information about Raptor can be found [[TestEngineering/Performance/Raptor|here]].
+A guide to handling Raptor regressions can be found [[TestEngineering/Performance/Running_performance_tests|here]].
+== Talos regressions ==
+For more information about Talos tests please visit the [https://firefox-source-docs.mozilla.org/testing/perfdocs/talos.html#test-definitions test documentation], and for more information about running Talos tests please go to [[TestEngineering/Performance/Talos/Running|Running Talos]].
+Guide to handling Talos regressions you can find [[TestEngineering/Performance/Running_performance_tests|here]].
+== AWSY regressions ==
+More information about AWSY results can be found [[AWSY/Tests|here]].
+== Build metrics regressions ==
+More information about build metrics results can be found [https://firefox-source-docs.mozilla.org/performance/build_metrics/build_metrics.html here]
+= Policies =
 == Policy #1: Backouts within 48-hours for large regressions ==
@@ Line 54: / Line 75: @@
 ==== See also ====
-* [https://wiki.mozilla.org/Buildbot/Talos/Sheriffing Regression sheriffing] - how are regressions detected and associated with patches.
+* [https://wiki.mozilla.org/TestEngineering/Performance/Sheriffing/Workflow Sheriffing workflow] - how are regressions detected and associated with patches.