342
edits
TestEngineering/Performance/FAQ: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/FAQ (view source)
Revision as of 13:03, 16 January 2020
, 16 January 2020→Tree
Alexandrui (talk | contribs) (→Tree) |
Alexandrui (talk | contribs) (→Tree) |
||
| Line 32: | Line 32: | ||
Note the two pushes that have no data (circled in red). If the regression happened around here, we might want to backfill those two jobs so we can ensure we are looking at the push which caused the regression instead of >1 push. | Note the two pushes that have no data (circled in red). If the regression happened around here, we might want to backfill those two jobs so we can ensure we are looking at the push which caused the regression instead of >1 push. | ||
=== What is an uplift === | |||
Every [[RapidRelease/Calendar|6 weeks]] we release a new version of Firefox. When we do that, our code which developers check into the nightly branch gets uplifted (thing of this as a large [[TestEngineering/Performance/Sheriffing/Tree_FAQ#What_is_a_merge|merge]]) to the Beta branch. Now all the code, features, and Talos regressions are on Beta. | |||
This affects the Performance Sheriffs because we will get a big pile of alerts for Mozilla-Beta. These need to be addressed rapidly. Luckily almost all the regressions seen on Mozilla-Beta will already have been tracked on Mozilla-Inbound or Autoland. | |||
==Alert== | ==Alert== | ||