Bug 786377 (tegra-299)

tegra-299 problem tracking

RESOLVED FIXED

Status

Release Engineering
Buildduty
RESOLVED FIXED
6 years ago
9 months ago

People

(Reporter: bhearsum, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

6 years ago
Didn't come back from a PDU reboot.
(Reporter)

Comment 1

6 years ago
Back in production.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Component: Release Engineering → Release Engineering: Machine Management
OS: All → Android
QA Contact: release → armenzg
Hardware: All → ARM
No jobs taken on this device for >= 7 weeks
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Updated

5 years ago
Depends on: 838687
had to stop and start clientproxy to make this happy again.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago5 years ago
Resolution: --- → FIXED

Comment 4

5 years ago
7 days without taking a job.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → FIXED
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
(Reporter)

Comment 5

4 years ago
2014-01-16 10:24:13 tegra-299 p    online   active  OFFLINE :: error.flg [Automation Error: Unable to connect to device after 5 attempts] 

pdu reboot didn't help
Status: RESOLVED → REOPENED
Depends on: 960642
Resolution: FIXED → ---
SD Card have been wiped and Tegra have been flashed.

Comment 7

4 years ago
error.flg is currently set to:

Automation Error: Unable to connect to device after 5 attempts

tegra may need a re-image, or at the very least, make sure it's properly re-attached to the network.

Updated

4 years ago
Depends on: 977305

Comment 8

4 years ago
tegra reimaged and flashed.


[vle@admin1a.private.scl3 ~]$ telnet tegra-299.tegra.releng.scl3.mozilla.com 20701
Trying 10.26.85.239...
Connected to tegra-299.tegra.releng.scl3.mozilla.com.
Escape character is '^]'.
$>^]
Power cycled, waited a day.

error.flg: Automation Error: Unable to connect to device after 5 attempts

Failed to reformat SD card:

$>exec newfs_msdos -F 32 /dev/block/vold/179:9
newfs_msdos: /dev/block/vold/179:9: No such file or directory
return code [1]
Depends on: 991259
in production running green

it did have one robocop retry with:
devicemanager.DMError: DeviceManager: Error reading file to push
Error deleting /data/anr/traces.txt

looking at https://tbpl.mozilla.org/?showall=all&tree=Mozilla-Inbound&jobname=robocop

it seems robocop jobs retry very often so I am skeptical to thinking this is a machine fault. I will resolve on this basis.
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.