Closed Bug 644120 Opened 14 years ago Closed 14 years ago

Don't use _nextFastReservedSlave for some release builders

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rail, Assigned: rail)

References

Details

(Whiteboard: [releases][automation])

Attachments

(1 file)

buildbotcustom
7.91 KB, patch
bhearsum
: review+
rail
: checked-in+
Details | Diff | Splinter Review
Some of the release builders don't require fast slaves to run. Some of them: permission checks, antivirus, push_to_mirrors, bouncer submitters. Additionally we could use slaves not only on linux platform. We hit this issue during 3.6.16 push to mirrors. Armen had to move one of the IX slaves to the master to run the builder.
Attached patch buildbotcustom — — Splinter Review
* removed nextSlave from some builders * used linux and mac slaves for those builders * used all slaves for dummy builders
Attachment #521209 - Flags: review?(bhearsum)
Priority: P3 → P2
Comment on attachment 521209 [details] [diff] [review] buildbotcustom Have you tested a run of av, permissions, or push to mirrors on a Mac? I doubt anything wouldn't work, but it'd be nice to know for sure!
Attachment #521209 - Flags: review?(bhearsum) → review+
(In reply to comment #2) > Have you tested a run of av, permissions, or push to mirrors on a Mac? I doubt > anything wouldn't work, but it'd be nice to know for sure! Tested, nothing unusual nor unexpected.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: