160
edits
TestEngineering/Performance/Sheriffing/Tree FAQ: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Sheriffing/Tree FAQ (view source)
Revision as of 12:56, 16 January 2018
, 16 January 2018update paragraph
(remove extra brackets) |
(update paragraph) |
||
| Line 1: | Line 1: | ||
= Branch names and confusion = | = Branch names and confusion = | ||
We have a variety of branches at Mozilla, here are the main ones that we see alerts on: | We have a variety of branches at Mozilla, here are the main ones that we see alerts on: | ||
* Mozilla-Inbound | * Mozilla-Inbound (PGO, Non-PGO) | ||
* | * Autoland (PGO, Non-PGO) | ||
* Mozilla-Beta (all PGO) | * Mozilla-Beta (all PGO) | ||
Linux and Windows builds have [[https://wiki.mozilla.org/Buildbot/Talos/Sheriffing/Tree_FAQ#What_is_PGO PGO]], OSX does not. | Linux and Windows builds have [[https://wiki.mozilla.org/Buildbot/Talos/Sheriffing/Tree_FAQ#What_is_PGO PGO]], OSX does not. | ||
When investigating alerts, always look for the Non-PGO branch first. Usually expect to find changes on Mozilla-Inbound (about | When investigating alerts, always look for the Non-PGO branch first. Usually expect to find changes on Mozilla-Inbound (about 50%) and Autoland (50%). | ||
The volume on the branches is something to be aware of, we have higher volume on Mozilla-Inbound and | The volume on the branches is something to be aware of, we have higher volume on Mozilla-Inbound and Autoland, this means that alerts will be generated faster and it will be easier to track down the offending revision. | ||
A final note, | A final note, Mozilla-Beta is a branch where little development takes place. The volume is really low and alerts come 5 days (or more) later. It is important to address Mozilla-Beta alerts ASAP because that is what we are shipping to customers. | ||
= What is coalescing = | = What is coalescing = | ||