741684 - (tegra-222) tegra-222 problem tracking

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task)

Description

[Phil Ringnalda (:philor)]

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.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

Disabled with stop_cp.

Comment 2

[Justin Wood (:Callek)]

Disabling this again, and setting the magic whiteboard so we don't lose track

Comment 3

[Jake Watkins [:dividehex]]

Re-imaged and initialized.

Comment 4

[Justin Wood (:Callek)]

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

Comment 5

[Aki Sasaki (not active)]

This went back down within a day or two of coming back up.

Comment 6

[Jake Watkins [:dividehex]]

tegra-222 has been pulled and put on :ctalbert's desk for testing

Comment 7

[Armen [:armenzg]]

This seems like a decomissioned tegra. I will remove it from production_config.py.

Comment 8

[Mike Taylor [:bear]]

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

Comment 9

[Mike Taylor [:bear]]

(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

Comment 10

[[e-mail] (:bhearsum)]

There's nothing actionable for buildduty here while this is in Clint's/Callek's hands.

Comment 11

[Chris Cooper [:coop] (he/him)]

(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?