Closed
Bug 786377
(tegra-299)
Opened 12 years ago
Closed 10 years ago
tegra-299 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Unassigned)
References
()
Details
Didn't come back from a PDU reboot.
Reporter | ||
Comment 1•12 years ago
|
||
Back in production.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Component: Release Engineering → Release Engineering: Machine Management
OS: All → Android
QA Contact: release → armenzg
Hardware: All → ARM
Comment 2•11 years ago
|
||
No jobs taken on this device for >= 7 weeks
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 3•11 years ago
|
||
had to stop and start clientproxy to make this happy again.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Comment 4•11 years ago
|
||
7 days without taking a job.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Reporter | ||
Comment 5•10 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
Comment 6•10 years ago
|
||
SD Card have been wiped and Tegra have been flashed.
Comment 7•10 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.
Comment 8•10 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 '^]'. $>^]
Comment 9•10 years ago
|
||
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]
Comment 10•10 years ago
|
||
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
Closed: 11 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
•