Closed Bug 840958 Opened 11 years ago Closed 11 years ago

comm-esr17 nightly builds are not being run

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: standard8, Unassigned)

References

Details

In bug 837146 we tried fixing the Mac debug builds so that they are green. This is now the case, but there's been no nightly builds triggered today.

I've additionally tried manually forcing the nightly builds, and again, no builds have started.
So, the first green Mac debug build I see is on dcc1993f148f, which is the same changeset that windows started burning on. So I don't see any changeset that would've been acceptable to the Nightly scheduler.

The manually triggered ones not running is very concerning though. How did you trigger them?
I just had a gander at the buildapi code at AFAICT  it's expected that forced nightlies don't work unless there's already been a nightly on that branch:
https://github.com/mozilla/build-buildapi/blob/master/buildapi/scripts/selfserve-agent.py#L459 calls https://github.com/mozilla/build-buildapi/blob/master/buildapi/scripts/selfserve-agent.py#L379, which does a 'select distinct buildername' query.

Found the self serve logs, which confirm this:
2013-02-13 04:05:51,133 New nightly by mbanner@mozilla.com of comm-esr17 dcc1993f148f
2013-02-13 04:06:10,603 buildernames are []


So, I think this is FIXED now that I've triggered one manual set of nightlies.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.