Bug 740448 (tegra-240)

tegra-240 problem tracking

RESOLVED FIXED

Status

P3
normal
RESOLVED FIXED
7 years ago
3 months ago

People

(Reporter: coop, Unassigned)

Tracking

Details

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

(Reporter)

Description

7 years ago
tegra-240 has been offline for 29 days according to last-build-per-slave.html.

Updated

6 years ago
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
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
Depends on: 959689
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Comment 2

5 years ago
SD card flashed/reimaged.
Took two jobs, died again. Not sure what to do .
(Reporter)

Updated

5 years ago
Assignee: bear → nobody

Updated

5 years ago
Depends on: 968568

Comment 4

5 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

5 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
Back in production.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago5 years ago
Resolution: --- → FIXED

Updated

3 months ago
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.