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)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
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
|
||
Comment 1•13 years ago
|
||
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.
|
Reporter | |
Comment 2•13 years ago
|
||
(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?
|
|
||
Comment 3•13 years ago
|
||
This should be done by briar-patch as it groks Tegras now
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
|
Assignee | |
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
|
||
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
|
|
||
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•