Closed Bug 679890 Opened 13 years ago Closed 13 years ago

re-image tegra-030

Categories

(Infrastructure & Operations :: RelOps: General, task)

ARM
Android
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mozilla, Assigned: dividehex)

References

Details

(Whiteboard: [android_tier_1])

This is staging and has been disabled. IIRC it's in Haxxor and can be unplugged at will.
Out of curiosity, why -030? Out of necessity: will it be coming back, or should I replace it with one of the new ones?
030 is not part of a test that i'm doing with the lower numbered ones. it should be coming back
(In reply to Zandr Milewski [:zandr] from comment #1) > Out of necessity: will it be coming back, or should I replace it with one of > the new ones? (If you're asking how long I'll need it: I don't know exactly, but I think I could safely expect to be done with it within a week or so.)
Gotcha. I'm in SF today, but will source a power supply and deliver the machine to dholbert tomorrow.
Got the tegra (thanks!) Resolving.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Bug 652050 is no longer an issue, so I no longer need this tegra board. (Thanks for the use of it, and sorry for holding onto it so long.) Zandr (or whoever's appropriate), feel free to just grab it off my desk in MV -- 3rd floor #91, near conference rooms 3U / 3V. It's unplugged.
This should go into the spare pool, with the 3 that are already in that list.
Assignee: server-ops-releng → jwatkins
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
tegra-030 is now in haxxor with other spares. It will need to be re-imaged and put into its 'ready to deploy/swap' state.
Summary: please give tegra-030 to dholbert for debugging → re-image tegra-030
Tegra-030 has been re-imaged and set aside in the spare tegra pool.
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.