Closed
Bug 732879
(tegra-063)
Opened 13 years ago
Closed 11 years ago
tegra-063 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Unassigned)
References
()
Details
(Whiteboard: [buildduty])
Once upon a time, a month or two ago, it didn't totally suck, but over the last 200 runs instead of normal 80-90% green it has been 51.5% green. Maybe after an intervention it can stay clean and sober for a while longer.
Updated•13 years ago
|
Updated•13 years ago
|
Whiteboard: [buildduty]
Updated•13 years ago
|
Alias: tegra-063
Summary: Please disable tegra-063 and enroll it in tegra recovery → tegra-063
Comment 2•13 years ago
|
||
back in production.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Summary: tegra-063 → tegra-063 problem tracking
Comment 3•13 years ago
|
||
FYI, it was just down, (not pingable) in the middle of a reftest run, I just hard-powercycled it via PDU.
We'll get it added to recovery if it stays down (noting here for history)
Comment 4•12 years ago
|
||
Sending this slave to recovery
-->Automated reopening of bug
Comment 5•12 years ago
|
||
flashed and reimaged.
Updated•12 years ago
|
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 13 years ago → 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Comment 6•11 years ago
|
||
SD card formatted, tegra reimaged and flashed.
[vle@admin1a.private.scl3 ~]$ fping tegra-063.tegra.releng.scl3.mozilla.com
tegra-063.tegra.releng.scl3.mozilla.com is alive
Comment 7•11 years ago
|
||
Back in production
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 8•11 years ago
|
||
Power cycled, waited a day.
error.flg: Automation Error: Unable to connect to device after 5 attempts
SD card reformat failed:
$>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]
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 9•11 years ago
|
||
in production running green :)
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 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
•