Closed Bug 741476 Opened 13 years ago Closed 13 years ago

Tegra verify should Auto PDU Cycle a tegra in certain circumstances

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Type:
task
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: Callek, Unassigned)

References

Details

In the case that verify.py is unable to ping (after a series of attempts/failures likely best) or in the case it *IS* able to ping but after a sufficient time is unable to connect to SUTAgent on the tegra, we could/should do a PDU cycle automatically
I don't know if giving verify.py the ability to PDU cycle is a good spot for this - but I think I need to talk some messy details to see your point.
(In reply to Mike Taylor [:bear] from comment #1) > I don't know if giving verify.py the ability to PDU cycle is a good spot for > this - but I think I need to talk some messy details to see your point. Remind me, did we decide this is wontfix, and fodder for briarpatch improvements at some point?
This should be done by briar-patch as it groks Tegras now
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.