Closed Bug 740448 (tegra-240) Opened 13 years ago Closed 11 years ago

tegra-240 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
ARM
Android
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: coop, Unassigned)

References

(
URL
)

Details

(Whiteboard: [mobile][capacity][buildduty])

tegra-240 has been offline for 29 days according to last-build-per-slave.html.
Assignee: nobody → bear
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: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Depends on: 959689
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
SD card flashed/reimaged.
Took two jobs, died again. Not sure what to do .
Assignee: bear → nobody
Depends on: 968568
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.
sd card replaced, tegra flashed and reimaged. fping tegra-240.tegra.releng.scl3.mozilla.com tegra-240.tegra.releng.scl3.mozilla.com is alive
Back in production.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 11 years ago
Resolution: --- → FIXED
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.