Closed Bug 1204753 Opened 10 years ago Closed 10 years ago

Do something about the shortage of OS X build slaves while a release is running

Categories

(Release Engineering :: Release Automation, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

Details

From what I hear, this is probably the result of switching to 20 chunks of repacks, or maybe we've switched the way we do releases and we're doing more than one at once, or something else I don't know or haven't thought of. Recently, I've always been able to tell when a release was building, by looking at the pending count for non-Try Mac builds on https://secure.pub.build.mozilla.org/builddata/reports/slave_health/jacuzzis.html and then for the age of the oldest non-Try one in https://secure.pub.build.mozilla.org/buildapi/pending and then closing all (non-Try) trees, because when a release is building we wind up with more than an hour of backlog on Mac builds on m-i/m-c/b-i/f-t/m-a/etc.
This is apparently now causing an OS X build backlog, causing trees to be closed.
We reverted the changes we made in bug 1191633, the patch and review is over there too.
Status: NEW → RESOLVED
Closed: 10 years ago
Depends on: 1191633
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.