Closed Bug 778857 (tegra-130) Opened 13 years ago Closed 12 years ago

tegra-130 problem tracking

Categories

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

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
ARM
Android
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: coop, Unassigned)

References

(
URL
)

Details

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

No description provided.
Depends on: 778812
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 925895
Back in production.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 12 years ago
Resolution: --- → FIXED
last job: Sunday, October 20, 2013 9:29:07 AM
Status: RESOLVED → REOPENED
Depends on: 944498
Resolution: FIXED → ---
flashed and reimaged
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
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
Status: RESOLVED → REOPENED
Depends on: 960642
Resolution: FIXED → ---
SD card replaced & reimaged/flashed.
taking production jobs
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
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.