tegra buildslave remains after cp marks tegra as offline

RESOLVED FIXED

Status

Release Engineering
General
P2
normal
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: bear, Assigned: bear)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [android][tegra])

(Assignee)

Description

7 years ago
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)

Updated

7 years ago
Assignee: nobody → bear
Priority: -- → P2
Whiteboard: [android][tegra]

Updated

7 years ago
Blocks: 610600

Comment 1

7 years ago
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.
(Assignee)

Comment 2

7 years ago
this was fixed when cp was refactored for bug 610600 and the killPID loop was cleaned up
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.