-------- Original-Nachricht --------
Betreff: Re: mozilla-inbound backout policy subject to change (become
similar to autoland)
Von: Myk Melez <m...@mykzilla.org>
Datum: 2018-08-09 02:11
Boris Zbarsky wrote on 2018-06-26 21:53:
On 6/27/18 12:50 AM, Mike Hommey wrote:
Perma bustage of tier-2 jobs usually do.
Of a bunch of them, or of just one tier-2 job (but permanent bustage
across all pushes)?
My understanding was that tier-2 meant it can be broken for a bit
without backout happening. If that's not the case, how does it differ
from tier-1?
Tier 2 can permafail if there is an ETA for a fix the developer and the
sheriff have agreed upon. The backout of Myk's push was a mistake and
the sheriffs have been reminded to contact the developer if there issues
with tier 2 jobs after a push.
It remains relevant, as I just had a change [1] backed out immediately
for busting Btup, which is currently categorized as tier-2.
Sheriffing/Job Visibility Policy [2] describes tier-2 as:
Jobs are shown by default on Treeherder, but are not sheriff-managed.
Results will be shown on Treeherder "for information only". New test
failures/bustage will not result in a backout, but a tracking bug will
be filed when observed.
It seems like this document is either out-of-date, and the tier-2 policy
has changed, or Btup is miscategorized.
Tier 2 jobs are going to be re-evaluated if that tier is still suitable
or if it's something which should not be broken because we rely on it
(e.g. QuantumRender, Btup is also heading for this).
Sebastian
-myk
[1]
https://phabricator.services.mozilla.com/rMOZILLACENTRAL08fa47a24e89697e4e43177860b55cc28298bbff
[2]
https://wiki.mozilla.org/Sheriffing/Job_Visibility_Policy#Overview_of_the_Job_Visibility_Tiers
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
