Closed
Bug 1020294
Opened 10 years ago
Closed 9 years ago
Dynamic Jacuzzi Allocator shouldn't allow a job to have zero builders
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: pmoore, Unassigned)
References
Details
Today we had to disable the dynamic jacuzzi allocator, because there were builders with zero slaves defined: https://bugzilla.mozilla.org/show_bug.cgi?id=1020210
It should not be possible for the jacuzzi allocator to allow a builder to reduce to zero slaves - possible one slave is also not ideal, but I think one should be the absolute minimum.
Previously we had the same issue, so it seems to be a repeating pattern. In any case, a simple check that at least one slave exists in each builder list - otherwise abort - should be sufficient.
Reporter | ||
Updated•10 years ago
|
Blocks: byebyebuildduty
Reporter | ||
Comment 1•9 years ago
|
||
I'm guessing this was fixed, as I never heard it come up again. Ben, do you know?
Just doing some bug hygiene :)
Flags: needinfo?(bhearsum)
Comment 3•9 years ago
|
||
WONTFIX because we're killing off jacuzzis in bug 1231367.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•7 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•