Closed Bug 632499 Opened 13 years ago Closed 13 years ago

tegra buildslave remains after cp marks tegra as offline

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Platform:
All
Android
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bear, Assigned: bear)

References

Details

(Whiteboard: [android][tegra]) 

I appears that some buildslaves are left running after cp has flagged a tegra as offline and stops monitoring.

Two things need to happen - find out why and add a check during monitor loop to detect if/when this has happened
Assignee: nobody → bear
Priority: -- → P2
Whiteboard: [android][tegra]
Blocks: 610600
During the mtv outage, this is causing staging to burn, but production seems ok ?
I wonder what the difference is, other than master buildbot versions.
this was fixed when cp was refactored for bug 610600 and the killPID loop was cleaned up
Status: NEW → RESOLVED
Closed: 13 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.