Closed
Bug 740448
(tegra-240)
Opened 12 years ago
Closed 10 years ago
tegra-240 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Unassigned)
References
()
Details
(Whiteboard: [mobile][capacity][buildduty])
tegra-240 has been offline for 29 days according to last-build-per-slave.html.
Updated•12 years ago
|
Assignee: nobody → bear
Comment 1•12 years ago
|
||
Last Week PDU Cycled Verify.py run, it attempts to updateSUT Came back (pingable) unable to connect to socket after 5 minutes OK AFTER THIS Running fine right now
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 2•10 years ago
|
||
SD card flashed/reimaged.
Comment 3•10 years ago
|
||
Took two jobs, died again. Not sure what to do .
Reporter | ||
Updated•10 years ago
|
Assignee: bear → nobody
Comment 4•10 years ago
|
||
adding to the 'replace sdcard' group. I am going to add tegras like this that have recently reimaged but fail almost immediately after being brought back in production.
Comment 5•10 years ago
|
||
sd card replaced, tegra flashed and reimaged. fping tegra-240.tegra.releng.scl3.mozilla.com tegra-240.tegra.releng.scl3.mozilla.com is alive
Comment 6•10 years ago
|
||
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 10 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 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
•