On Tue, Jun 26, 2018 at 3:54 PM Gregory Szorc <g...@mozilla.com> wrote:
> On Tue, Jun 26, 2018 at 3:45 PM, Dave Townsend <dtowns...@mozilla.com> > wrote: > >> On Tue, Jun 26, 2018 at 3:06 PM Sebastian Hengst <a...@gmx.de> wrote: >> >> > -------- Original-Nachricht -------- >> > Betreff: Re: mozilla-inbound backout policy subject to change (become >> > similar to autoland) >> > Von: Boris Zbarsky <bzbar...@mit.edu> >> > Datum: 2018-06-24 21:28 >> > > On 6/19/18 9:04 AM, Sebastian Hengst wrote: >> > >> TL;DR: We would like to change the mozilla-inbound backout policy to >> > >> be like autoland’s. >> > > >> > > This seems like a pretty reasonable change in general. >> > > >> > > Is there a well-documented try syntax string which corresponds to >> "these >> > > are the things that need to be green to avoid being backed out"? >> > > Presumably that string is not "-p all -u all" because it should >> exclude >> > > tier2 and lower things, but it's not entirely clear to me what the >> > > autoland backout criteria are. I would assume we want developers to >> do >> > > a try run with that syntax before pushing to inbound as needed. >> > > >> > > -Boris >> > >> > The recommend Try practices can be found at >> > https://wiki.mozilla.org/Sheriffing/How_To/Recommended_Try_Practices >> >> >> This doesn't seem to answer the question. I frequently do patches where I >> can't reliably guess the extent of test breakage and want to run a full >> set >> to be on the safe side. What try configuration gives us tier 1 results >> only? >> > > I agree that the default behavior of `-p all -u all -t all` is running too > much and confusing people. I filed bug 1471404 to change the behavior. > > Will that be sufficient to fix the issue? > Sounds good to me. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
