Closed Bug 655440 Opened 13 years ago Closed 13 years ago

Need an automated way to spot a slave which is taking just a second or two to burn a job, over and over again

Categories

(Release Engineering :: General, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 655492

People

(Reporter: philor, Unassigned)

References

Details

Bug 655437 is about a Mac slave which got into whatever sort of broken filesystem trouble "Device not configured" is, which allowed it to do a test job in between 0 and 2 seconds, which allowed it to burn more than 500 test jobs in less than a day and a half.

We need some better detection for that than me noticing that a particular job was missing on a couple of pushes, and going off to Tinderbox to see why.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.