Closed Bug 741684 (tegra-222) Opened 12 years ago Closed 12 years ago

tegra-222 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
ARM
Android
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

(
URL
)

Details

(Whiteboard: [buildslave][capacity][mobile]) 

Oops, I jinxed it: first bug 720073 comment 77, and now something broke on it last Monday, and its last 144 runs have all been red when the purple doesn't get there first.
Disabled with stop_cp.
Disabling this again, and setting the magic whiteboard so we don't lose track
Assignee: nobody → bugspam.Callek
Whiteboard: [buildduty][buildslave][capacity][mobile]
Depends on: 758040
No longer depends on: 758040
Depends on: 760195
Re-imaged and initialized.
Left this unassigned for now, will cycle back in when others go bad.

http://hg.mozilla.org/build/tools/rev/dd9fd5111799 - removed _comment in tegras.json
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
This went back down within a day or two of coming back up.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 762696
tegra-222 has been pulled and put on :ctalbert's desk for testing
This seems like a decomissioned tegra. I will remove it from production_config.py.
Summary: Please disable tegra-222 and enroll it in tegra recovery → tegra-222 problem tracking
it's not technically decommissioned - just in limbo until :ctalbert gets to it
(In reply to Mike Taylor [:bear] from comment #8)
> it's not technically decommissioned - just in limbo until :ctalbert gets to
> it

I've updated inventory to reflect this status change
There's nothing actionable for buildduty here while this is in Clint's/Callek's hands.
Whiteboard: [buildduty][buildslave][capacity][mobile] → [buildslave][capacity][mobile]
(In reply to Mike Taylor [:bear] from comment #8)
> it's not technically decommissioned - just in limbo until :ctalbert gets to
> it

Have any tegras actually come back from this limbo state?
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Assignee: bugspam.Callek → nobody
QA Contact: armenzg → bugspam.Callek
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.