Closed Bug 960643 (tegra-357) Opened 12 years ago Closed 11 years ago

tegra-357 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

ARM
Android

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned)

References

Details

(Whiteboard: [buildduty][buildslaves][capacity])

2014-01-16 10:05:45 tegra-357 p online active OFFLINE :: error.flg [Automation Error: Unable to connect to device after 5 attempts]
tegra's SD replaced, reimaged and flashed.
Back in production.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Depends on: foopy32
Resolution: FIXED → ---
All tegras are being decommissioned.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → WONTFIX
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.