TestEngineering/Performance/Sheriffing/Tree FAQ: Difference between revisions

remove extra brackets
(remove extra brackets)
(remove extra brackets)
Line 50: Line 50:


= What is a backout =
= What is a backout =
Many times we backout or hotfix code as it is causing a build failure or unittest failure.  The [[https://wiki.mozilla.org/Sheriffing/Sheriff_Duty Sheriff team]] handles this process in general and backouts/hotfixes are usually done within 3 hours (i.e. we won't have [[https://wiki.mozilla.org/Buildbot/Talos/Sheriffing/Noise_FAQ#Why_do_we_need_12_future_data_points 12 future changesets]]) of the original fix.  As you can imagine we could get an alert 6 hours later and go to look at the graph and see there is no regression, instead there is a temporary spike for a few data points.
Many times we backout or hotfix code as it is causing a build failure or unittest failure.  The [https://wiki.mozilla.org/Sheriffing/Sheriff_Duty Sheriff team] handles this process in general and backouts/hotfixes are usually done within 3 hours (i.e. we won't have [https://wiki.mozilla.org/Buildbot/Talos/Sheriffing/Noise_FAQ#Why_do_we_need_12_future_data_points 12 future changesets]) of the original fix.  As you can imagine we could get an alert 6 hours later and go to look at the graph and see there is no regression, instead there is a temporary spike for a few data points.


While looking on TreeHerder for a backout, they all mention a backout in the commit message:
While looking on TreeHerder for a backout, they all mention a backout in the commit message:
160

edits