Closed
Bug 778857
(tegra-130)
Opened 12 years ago
Closed 10 years ago
tegra-130 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: coop, Unassigned)
References
()
Details
(Whiteboard: [buildduty][buildslaves][capacity])
No description provided.
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•11 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 1•11 years ago
|
||
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Comment 2•11 years ago
|
||
last job: Sunday, October 20, 2013 9:29:07 AM
Comment 3•11 years ago
|
||
flashed and reimaged
Comment 4•11 years ago
|
||
Back in production.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 5•10 years ago
|
||
2014-01-16 10:15:25 tegra-130 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 replaced & reimaged/flashed.
Comment 7•10 years ago
|
||
taking production jobs
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
•