canmove, Confirmed users
1,126
edits
Sheriffing/Job Visibility Policy: Difference between revisions
m
→4) Scheduled on every push: Clarify coalescing
m (→The future: Add missing parens) |
m (→4) Scheduled on every push: Clarify coalescing) |
||
| Line 26: | Line 26: | ||
* Otherwise job failures will not be attributable to a single changeset, resulting in either tree closure or backout of multiple pushes (see requirement #2). | * Otherwise job failures will not be attributable to a single changeset, resulting in either tree closure or backout of multiple pushes (see requirement #2). | ||
* An exception is made for nightly builds with an virtually equivalent non-nightly variant that is built on every push & for tests run on PGO builds (given that PGO builds take an inordinate amount of time, we still schedule them every 3/6 hours depending on tree, and relatively speaking there any not too many PGO-only test failures). | * An exception is made for nightly builds with an virtually equivalent non-nightly variant that is built on every push & for tests run on PGO builds (given that PGO builds take an inordinate amount of time, we still schedule them every 3/6 hours depending on tree, and relatively speaking there any not too many PGO-only test failures). | ||
* Note also that coalescing (buildbot queue collapsing when there is more than one queued job) may mean that not all scheduled jobs actually get run. Whilst coalescing makes sheriffing harder, it's a necessary evil given that automation infrastructure demand frequently outstrips supply. | * Note also that coalescing (buildbot queue collapsing when there is more than one queued job of the exact same tree/type) may mean that not all scheduled jobs actually get run. Whilst coalescing makes sheriffing harder, it's a necessary evil given that automation infrastructure demand frequently outstrips supply. | ||
=== 5) Easily run on try server === | === 5) Easily run on try server === | ||