Bug 741684 (tegra-222)

tegra-222 problem tracking

RESOLVED FIXED

Status

Infrastructure & Operations
CIDuty
RESOLVED FIXED
6 years ago
2 months ago

People

(Reporter: philor, Unassigned)

Tracking

Details

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

(Reporter)

Description

6 years ago
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]

Updated

6 years ago
Depends on: 758040

Updated

6 years ago
No longer depends on: 758040

Updated

6 years ago
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
Last Resolved: 6 years ago
Resolution: --- → FIXED

Comment 5

6 years ago
This went back down within a day or two of coming back up.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Updated

6 years ago
Depends on: 762696
tegra-222 has been pulled and put on :ctalbert's desk for testing

Comment 7

6 years ago
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

Comment 8

6 years ago
it's not technically decommissioned - just in limbo until :ctalbert gets to it

Comment 9

6 years ago
(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
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED

Updated

6 years ago
Blocks: 778192
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering

Updated

4 years ago
Assignee: bugspam.Callek → nobody
QA Contact: armenzg → bugspam.Callek

Updated

2 months ago
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.