Closed
Bug 835371
Opened 13 years ago
Closed 13 years ago
Remove nextL10nSlave support
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: catlee)
Details
(Whiteboard: [buildbot][cleanup])
Attachments
(1 file)
|
7.58 KB,
patch
|
bhearsum
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
We currently restrict l10n jobs to running on the first N connect slaves for any particular builder. My recollection is that we used to do this to prevent l10n jobs from consuming all build resources early in the morning, and also to reduce the load on hg/ftp.
I think we should remove these restrictions. Right now with so many masters and slaves, it's resulted in plenty of available slave capacity and really long backlog of l10n jobs.
To address the load concerns, we could introduce some kind of builder-level lock so that no more than N l10n jobs are running at once and/or use builder prioritization to make l10n jobs a lower priority that other jobs.
|
Assignee | |
Updated•13 years ago
|
Whiteboard: [buildbot] → [buildbot][cleanup]
|
||
Comment 2•13 years ago
|
||
Comment on attachment 709151 [details] [diff] [review]
remove nextL10nSlave
Review of attachment 709151 [details] [diff] [review]:
-----------------------------------------------------------------
Nope! mxr helped me verify that this is ok.
Attachment #709151 -
Flags: review?(bhearsum) → review+
|
|
Assignee | |
Updated•13 years ago
|
Attachment #709151 -
Flags: checked-in+
|
|
Assignee | |
Updated•13 years ago
|
Assignee: nobody → catlee
|
|
Assignee | |
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
|
||
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
•