Closed
Bug 519868
Opened 15 years ago
Closed 14 years ago
Audit slave directory on mac try slaves
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jhford, Unassigned)
Details
while doing the puppet rollout on the mac slaves I have found that some of the slaves are using /builds/slave for the slave directory and some are using /builds/buildbot/sendchange-slave This could cause maintainance trouble now that we have puppet. I did find that the ones that are running in the alternate location also have a slave in /builds/slave but they appear not to be running from there. My rough guess is that 01,02,03,04,06,07 are running from the sendchange-slave directory and the others are from /builds/slave.
Reporter | ||
Comment 1•15 years ago
|
||
further inspection looks like it is limited to 01 and 02 though the others previously mentioned do have the remnants of using the sendchange-slave directory including a twistd.pid file.
Comment 2•14 years ago
|
||
Mass move of bugs from Release Engineering:Future -> Release Engineering. See http://coop.deadsquid.com/2010/02/kiss-the-future-goodbye/ for more details.
Component: Release Engineering: Future → Release Engineering
Priority: -- → P3
Reporter | ||
Comment 3•14 years ago
|
||
this isn't presenting itself as a major issue. If this comes up again please reopen
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•