Closed Bug 1095302 Opened 10 years ago Closed 6 years ago

Slaverebooter shouldn't graceful a slave which hasn't done a build for 5 hours because it was just returned to production

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: philor, Unassigned)

Details

The story behind https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slave.html?class=try&type=bld-lion-r5&name=bld-lion-r5-028 is

* slave disabled for a reimage
* reimaged and returned to production at 5:32:55 PM
* at 5:44:30 PM, slaverebooter says "hey, this slave hasn't done a job for 8 days, I should graceful it"
* at 6:31:46 PM, it shuts down and sits idle until at 9:01:17 PM I see what it did there and reboot it

In the current scheme of things, when buildduty sees that we're lagging, and heroically rushes all possible slaves back into production, he gets exactly one job out of them before they sit idle.
Component: Tools → General
I think this bug outlived its usefulness. We moved to TC in the meantime.
Closing this, feel free to reopen if I'm wrong.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.