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?
By redeploy, do you mean re-image with an eg, 10.6 image?
I assume they're mini's, so there are even more options than 10.6, but yes, that's what I mean.
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.
Assigning to dustin since he's already doing the monitoring here.
Assignee: nobody → dustin
OS: All → Mac OS X
Priority: -- → P3
Hardware: All → x86
This particular silo seems fine lately.
Status: NEW → RESOLVED
Last Resolved: 7 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.