Closed
Bug 626857
Opened 13 years ago
Closed 13 years ago
moz2-darwin9-slaveNN going idle for days
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
Details
(Whiteboard: [buildslaves])
As far as I can tell, this is expected, as there just aren't enough jobs to keep these busy - they mostly do 191 and 192 tests, with only leak tests run on m-c. In the short term, I've been restarting the machines to keep the logs fresh, but instead I'll start ack'ing them to this bug. Should we redeploy some of these builders to other pools?
Comment 1•13 years ago
|
||
By redeploy, do you mean re-image with an eg, 10.6 image?
Assignee | ||
Comment 2•13 years ago
|
||
I assume they're mini's, so there are even more options than 10.6, but yes, that's what I mean.
Assignee | ||
Comment 3•13 years ago
|
||
I'm tracking this for the week in the slave spreadsheet. I haven't seen many idle slaves from this silo, so we may be back on track.
Comment 4•13 years ago
|
||
Assigning to dustin since he's already doing the monitoring here.
Assignee: nobody → dustin
OS: All → Mac OS X
Priority: -- → P3
Hardware: All → x86
Whiteboard: [buildslaves]
Assignee | ||
Comment 5•13 years ago
|
||
This particular silo seems fine lately.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
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
•