Closed
Bug 731814
Opened 13 years ago
Closed 13 years ago
Add checks to master configs that we're not exceeding our # builders / slave limit
Categories
(Release Engineering :: General, enhancement, P2)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: catlee)
References
Details
(Whiteboard: [buildmasters])
Attachments
(1 file)
|
4.36 KB,
patch
|
bhearsum
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
We should be able to add an assertion in master.cfg that we're not exceeding 1000 builders per slave. This would cause changes that increase the number of builders beyond this limit to break test-masters.
|
||
Updated•13 years ago
|
Component: Release Engineering → Release Engineering: Automation
QA Contact: release → catlee
Whiteboard: [buildmasters]
|
Assignee | |
Updated•13 years ago
|
Assignee: nobody → catlee
Severity: normal → enhancement
Priority: -- → P2
|
|
Assignee | |
Comment 1•13 years ago
|
||
Attachment #603317 -
Flags: review?(bhearsum)
|
||
Updated•13 years ago
|
Attachment #603317 -
Flags: review?(bhearsum) → review+
|
|
Assignee | |
Updated•13 years ago
|
Attachment #603317 -
Flags: checked-in+
|
|
Assignee | |
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
|
||
Comment 2•13 years ago
|
||
This change went live in a reconfiguration around 9AM.
|
||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
|
|
||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•