Closed
Bug 731631
Opened 12 years ago
Closed 12 years ago
tegra-284 recovery
Categories
(Infrastructure & Operations :: RelOps: General, task, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bear, Unassigned)
References
Details
(Whiteboard: [buildduty][buildslave][capacity])
This tegra has a huge number of failed tests across the board. Can it poked and prodded to see if anything is wrong with the SD card?
Reporter | ||
Updated•12 years ago
|
Whiteboard: [buildduty][buildslave][tegra]
Updated•12 years ago
|
Assignee: server-ops-releng → mlarrain
colo-trip: --- → mtv1
Comment 1•12 years ago
|
||
reimaged device and noted in a spreadsheet for tracking
Assignee: mlarrain → nobody
Status: NEW → ASSIGNED
Component: Server Operations: RelEng → Release Engineering
QA Contact: arich → release
Updated•12 years ago
|
Component: Release Engineering → Release Engineering: Machine Management
Priority: -- → P3
Whiteboard: [buildduty][buildslave][tegra] → [buildduty][buildslave][capacity]
Comment 2•12 years ago
|
||
We're tracking releng stuff in the slave specific bugs, moving this back and resolving - thanks!
Assignee: nobody → server-ops-releng
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Component: Release Engineering: Machine Management → Server Operations: RelEng
QA Contact: release → arich
Resolution: --- → FIXED
Updated•11 years ago
|
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•