1104765 - Nightly builds from November 24th were built from a mid-merge changeset

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect)

Description

[Dave Townsend [:mossop]]

Treeherder shows the Nightly builds from November 24th being built from changeset 8c02f3280d0c. This was a change to disable e10s by default so I was surprised when I updated to find that e10s was still enabled.

On ftp there are two nightly builds from 24th, was a retrigger done?

The first matches what treeherder shows: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014/11/2014-11-24-03-02-07-mozilla-central/

The second matches my build: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2014/11/2014-11-24-10-01-36-mozilla-central/

The strange part is that my build was built from be4ba3d5ca9a. Pushlog shows that this changeset was never a head on mozilla-central, it was pushed after the e10s changeset as part of a merge (https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=be4ba3d5ca9a). Because the build used a changeset before the actual merge changeset it didn't include the e10s change and presumably any m-c changes since the last merge from inbound.

It sounds like a bug to be able to have nightly builds built from changesets in the middle of a merge like this since as we see here a second nightly can regress behaviour from a first.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

The builds on be4ba3d5ca9a were forced by Marcia using self-serve, for bug 1085759 by the looks. That revision was later than 1st nightly, but I agree is unusual in that it's in the middle of a merge rather than the top of one.

Mossop, are you still not getting an update ? If so, could you please capture the query url, eg with app.update.log set to true. I downloaded the mac build from the 2nd url above and get offered the 20141125030206 nightly.

Comment 2

[Dave Townsend [:mossop]]

(In reply to Nick Thomas [:nthomas] from comment #1)
> The builds on be4ba3d5ca9a were forced by Marcia using self-serve, for bug
> 1085759 by the looks. That revision was later than 1st nightly, but I agree
> is unusual in that it's in the middle of a merge rather than the top of one.
> 
> Mossop, are you still not getting an update ? If so, could you please
> capture the query url, eg with app.update.log set to true. I downloaded the
> mac build from the 2nd url above and get offered the 20141125030206 nightly.

I got the new update I just think it's very confusing to be able to do nightlies from mid-merge changesets like that. Maybe we could add some method to block it.