Maple nightlies not building

RESOLVED WORKSFORME

Status

Release Engineering
General
P5
normal
RESOLVED WORKSFORME
7 years ago
5 years ago

People

(Reporter: GPHemsley, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [pending response][buildduty], URL)

(Reporter)

Description

7 years ago
As I understand it, new nightly builds for the maple branch are supposed to be built whenever there are new commits, but not when there aren't.

However, I pushed new code a couple of days ago and while they generated builds right then and there, there were no nightlies generated from the code.

Thus, most maple nightlies remain at their July 19 version—except the 64-bit Windows builds, which somehow built on September 9 without me pushing any new commits.

Has something changed?
Assignee: server-ops → nobody
Component: Server Operations → Release Engineering
QA Contact: cshields → release
(In reply to Gordon P. Hemsley [:gphemsley] from comment #0)
> As I understand it, new nightly builds for the maple branch are supposed to
> be built whenever there are new commits, but not when there aren't.

There is another requirement - there must be successful compilations for opt and debug for all platforms. In this case 'Linux x86-64 maple build' failed to clone the repo and wasn't rebuilt. I'm short on context having been away for a week, but I think there was talk of making that kind of error be purple rather than red, and hence the job would be auto-retried.

It's now too late to correct that red compile and have nightlies be created automatically, so I suggest you go to
 https://build.mozilla.org/buildapi/self-serve/maple
and put the tipmost revision into the 'Create new nightly builds' form.
(Reporter)

Comment 2

7 years ago
(In reply to Nick Thomas [:nthomas] (out sick) from comment #1)
> (In reply to Gordon P. Hemsley [:gphemsley] from comment #0)
> > As I understand it, new nightly builds for the maple branch are supposed to
> > be built whenever there are new commits, but not when there aren't.
> 
> There is another requirement - there must be successful compilations for opt
> and debug for all platforms. In this case 'Linux x86-64 maple build' failed
> to clone the repo and wasn't rebuilt. I'm short on context having been away
> for a week, but I think there was talk of making that kind of error be
> purple rather than red, and hence the job would be auto-retried.

Yeah, that would've worked. I sent the non-nightly version for a rebuild and it built successfully (along with the two Windows builds that were purple).

> It's now too late to correct that red compile and have nightlies be created
> automatically, so I suggest you go to
>  https://build.mozilla.org/buildapi/self-serve/maple
> and put the tipmost revision into the 'Create new nightly builds' form.

I've tried that a couple of times and I get an 'OK' message, but I'm not getting any mention of it in the self-serve UI. Or... do I have to wait until nightly build time? (The short-form revision is fed0d9c8adf8.)

Comment 3

7 years ago
Hm.
I'm wondering if the size of the push, in terms of number of commits, is causing problems somewhere in here.

Can you try a dummy push that has a single commit?
You shouldn't have to wait for nightly build time for a nightly.

Comment 4

7 years ago
Ping?

Updated

7 years ago
Priority: -- → P5
Whiteboard: [pending response][buildduty]
(Reporter)

Comment 5

7 years ago
Sorry for the delay; I've been really busy with school.

Also, I kinda did the exact opposite of what you suggested: I just pushed a couple of merges from m-c: added 915 changesets with 7277 changes to 4865 files.

So that may not give us the answer we're looking for. If nightlies don't get built off of this, then I'll do what you actually suggested.

This isn't a particularly high-priority item, given how slow development goes on the maple branch, so not to worry.
Priority: P5 → --
(Reporter)

Updated

7 years ago
Priority: -- → P5
(Reporter)

Comment 6

7 years ago
It looks like my merge commit on October 7th triggered nightly builds correctly, so you can close this if you want.
(Reporter)

Comment 7

7 years ago
(In reply to Gordon P. Hemsley [:gphemsley] from comment #6)
> It looks like my merge commit on October 7th triggered nightly builds
> correctly, so you can close this if you want.

However, it does not appear that the old builds recognize it as a update. (Could it be the change in version numbers? My old build is 8, while the new builds are 10.)

Would that warrant a separate bug?
In one of those strange coincidences I'd realized the same problem over the weekend, and just filed bug 694873 for it.
--> WORKSFORME for the nightly builds.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.