tegra dashboard lists wrong foopy for some tegras

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
5 years ago
6 months ago

People

(Reporter: bhearsum, Unassigned)

Tracking

Details

Eg, foopy127, which is decommed. Looks like its tegras got moved to foopy128.

I haven't fully audited it to see if there's other wrong things.
just for reference slave health is accurate since it reads direct from devices.json that does not negate this bug though
Found in triage. 

Not sure if this should be RelEng:MachineManagement or RelEng:DeveloperTools, but RelEng:MachineManagement feels more likely, so starting there.
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: armenzg
(In reply to Justin Wood (:Callek) from comment #1)
> just for reference slave health is accurate since it reads direct from
> devices.json that does not negate this bug though

Actually I think it does, given bug 798056.

Drill-down from here for better info:

https://secure.pub.build.mozilla.org/builddata/reports/slave_health/slavetype.html?class=test&type=tegra

The tegra pages pull their info directly from devices.json which is assumed to be canonical.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering

Updated

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