TestEngineering/Performance/Talos/RegressionBugsHandling: Difference between revisions

TestEngineering/Performance/Talos/RegressionBugsHandling (view source)

16 bytes removed , 13 August 2015

m

no edit summary

Confirmed users

356

edits

@@ Line 24: / Line 24: @@
 The A-Team perf sheriffs will create a Talos regression bug as soon as a regression is confirmed using Talos re-triggers. The patch author and reviewer will be CC’ed, and if they don’t provide an explanation for why the regression is acceptable, the patch will be backed out. The goal is to back out unjustified regressions within 48 hours of them landing. We’d like to give the patch author about 24 hours to reply after the regression bug is filed.
-The A-Team has been working hard on improving the tools for understanding Talos regressions  (e.g. Perfherder + compare-talos), and we think debugging a Talos regression is a much less painful process these days. For example, there is now a highly useable view to visualize the comparison between a proposed patch against a baseline revision at https://treeherder.mozilla.org/perf.html#/comparechooser.
+The A-Team has been working hard on improving the tools for understanding Talos regressions  (e.g. Perfherder), and we think debugging a Talos regression is a much less painful process these days. For example, there is now a highly useable view to visualize the comparison between a proposed patch against a baseline revision at https://treeherder.mozilla.org/perf.html#/comparechooser.
 =Policy #2: Policy for smaller regressions =