Bug 750784 (tegra-029)

[staging] tegra-029 problem tracking

RESOLVED FIXED

Status

RESOLVED FIXED
7 years ago
6 months ago

People

(Reporter: armenzg, Unassigned)

Tracking

Details

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

(Reporter)

Description

7 years ago
tegra-029.build.mtv1:tegra agent check is CRITICAL: Connection refused

It hasn't taken any jobs since 2011-10-28 09:12:00

It is a staging slave though.
(Reporter)

Updated

7 years ago
Depends on: 750787
It has also been down since march, "last job per slave" iirc doesn't show details for staging slaves.

2012-03-09 10:30:23 tegra-029 s  INACTIVE   active  OFFLINE :: SUTAgent not present;

This likely needs to be re-flashed so that it has a SUTAgent and handed back to staging.
Summary: tegra-029 problem tracking → [staging] tegra-029 problem tracking
Whiteboard: [buildduty][buildslave][capacity]
nvram has been re-flashed and sdcard reinitialized
(Reporter)

Updated

7 years ago
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering

Updated

5 years ago
Depends on: 913321
Blocks: 925447
Watcher version needs upgrading - upgrade unsuccessful via script, requesting this tegra to be reimaged with the new image that has the latest Watcher (1.16).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Updated

5 years ago
No longer blocks: 925447
Depends on: 925447
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago5 years ago
Resolution: --- → FIXED

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.