As previously announced[1], Firefox builds now (or momentarily will) have a
hard-dependency on NodeJS 8.11.0 or newer.
Anyone (other than certain specific automation tasks) who has been using
--disable-nodejs in their mozconfig as a workaround for problems should now
remove this in order for
in the last 3
years.
[1] https://wiki.mozilla.org/Sheriffing/Job_Visibility_Policy
[2]
https://developer.mozilla.org/en-US/docs/Mozilla/Supported_build_configurations
Sebastian
Original-Nachricht
Betreff: mozilla-inbound backout policy subject to change (become
similar
Sebastian Hengst wrote on 2018-08-09 08:51:
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).
Good to know, thanks, Sebastian. Is there a way to track
Original-Nachricht
Betreff: Re: mozilla-inbound backout policy subject to change (become
similar to autoland)
Von: Myk Melez
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
On 8/8/18 8:11 PM, Myk Melez wrote:
Boris, did you ever get an answer to this question?
I did not.
-Boris
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
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
Just to add one other point to this discussion:
I *hate* backouts. I don't just mean of my patches. I mean in
general. Whenever I come across a backout in a blame walk or a
bisect, it makes my life much more difficult. And I know I'm not
alone in this.
I thought the policy for autoland was
On Wed, Jun 27, 2018 at 12:36:22AM -0400, Boris Zbarsky wrote:
> On 6/26/18 6:53 PM, Gregory Szorc wrote:
> > 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
On 6/26/18 6:53 PM, Gregory Szorc wrote:
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?
The proposal is to have that syntax run all tier1 and tier2
Also sprach Gregory Szorc:
> On Tue, Jun 26, 2018 at 3:45 PM, Dave Townsend
> wrote:
>
>> 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
>>
On Tue, Jun 26, 2018 at 3:54 PM Gregory Szorc wrote:
> On Tue, Jun 26, 2018 at 3:45 PM, Dave Townsend
> wrote:
>
>> On Tue, Jun 26, 2018 at 3:06 PM Sebastian Hengst wrote:
>>
>> > Original-Nachricht
>> > Betreff: Re: mozilla-inbound b
On Tue, Jun 26, 2018 at 3:45 PM, Dave Townsend
wrote:
> On Tue, Jun 26, 2018 at 3:06 PM Sebastian Hengst wrote:
>
> > Original-Nachricht
> > Betreff: Re: mozilla-inbound backout policy subject to change (become
> > similar to autoland)
> > Von:
On Tue, Jun 26, 2018 at 3:06 PM Sebastian Hengst wrote:
> Original-Nachricht
> Betreff: Re: mozilla-inbound backout policy subject to change (become
> similar to autoland)
> Von: Boris Zbarsky
> Datum: 2018-06-24 21:28
> > On 6/19/18 9:04 AM, Sebastian Hen
Original-Nachricht
Betreff: Re: mozilla-inbound backout policy subject to change (become
similar to autoland)
Von: Boris Zbarsky
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
The new policy will be used from now on.
- Sebastian
Original-Nachricht
Betreff: mozilla-inbound backout policy subject to change (become
similar to autoland)
Von: Sebastian Hengst
Datum: 2018-06-19 15:04
Hi,
If you don't push code to mozilla-inbound, you can stop reading
On Sun, Jun 24, 2018 at 03:28:45PM -0400, Boris Zbarsky wrote:
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
On Sun, Jun 24, 2018 at 03:28:45PM -0400, Boris Zbarsky wrote:
> 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
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
On 19/06/2018 15:04, Sebastian Hengst wrote:
> TL;DR: We would like to change the mozilla-inbound backout policy to be
> like autoland’s.
Sounds like a very good idea. When I screw up with a patch what worries
me most is wasting other peoples' time with a broken tree. Having
problematic patches
Hi,
If you don't push code to mozilla-inbound, you can stop reading now.
TL;DR: We would like to change the mozilla-inbound backout policy to be
like autoland’s.
In order to decrease tree closure times for inbound, allow for more
frequent merges from inbound to m-c, and ensure consistent
Yesterday a mass change was applied to bugzilla to move a set of bugs to a
RESOLVED: INACTIVE state.
Dealing with inactive bug reports has been a contentious issue in the
past. While I think it’s time for us to revisit that issue and make
different choices than we have in the past, a change of
It's the weekly report on the state of triage in Firefox-related components.
Marking Bugs for the Firefox 57 Release
The bug that will overshadow all the hard work we put into the Firefox 57
release has probably already been filed. We need to find it and fix it. If
you think a bug might affect
Hi,
To give a little insight into our work and make our work more visible to
our Community we decided to create a monthly report of what's going on in
the Sheriffs Team.
If you have questions or feedback, just let us know!
In case you don't know who the sheriffs are, or to check if there are
23 matches
Mail list logo
