Closed Bug 770513 (tegra-218) Opened 12 years ago Closed 10 years ago

tegra-218 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Unassigned)

References

()

Details

(Whiteboard: [buildduty])

      No description provided.
Depends on: 770519
Got this back up just now after a few PDU reboots and a cp stop/start cycle
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Last 49 jobs have been red or purple.
Status: RESOLVED → REOPENED
Depends on: 781554
Resolution: FIXED → ---
Depends on: 780798
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
And post-recovery, it managed 11 green builds, 1 orange, and has now been red for the last 11 in a row.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
ran stop_cp.sh on it.
Not sure what to do next. Callek?
Assignee: nobody → bugspam.Callek
Run stop_cp on it again? This time --with-fire?
(In reply to Phil Ringnalda (:philor) from comment #7)
> Run stop_cp on it again? This time --with-fire?

done
Depends on: 792316
IT handled this, start_cp run now
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
7 red in a row.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: tegra-218 problem tracking → [disable me] tegra-218 problem tracking
Assignee: bugspam.Callek → nobody
Ran stop_cp on it.
Summary: [disable me] tegra-218 problem tracking → tegra-218 problem tracking
[TODO Hand to recovery]
(In reply to Justin Wood (:Callek) from comment #13)
> [TODO Hand to recovery]

Is there a reason you didn't block the tegra-recovery bug when you made this comment? This Tegra has now sat idle for weeks for no good reason.
Depends on: 807663
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
36% green.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 808437
Ran ./stop_cp.sh
Blocks: 808468
Blocks: 813012
No longer blocks: 813012
This is back to taking job(s) and is up now.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
No longer blocks: 808468
Depends on: 808468
Pretty much worthless - today it took two jobs, RETRY on one; yesterday it took two jobs, RETRY on one; the day before zero jobs; the day before that two jobs, RETRY on one. The 22nd was a big day for it, seven jobs, RETRY on six.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Sending this slave to recovery
-->Automated message.
Depends on: 889567
Successfully recovered.
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
agent check failing; pdu reboot didn't help
Depends on: 922822
2014-01-16 10:22:49 tegra-218 p    online   active  OFFLINE :: error.flg [Automation Error: Unable to connect to device after 5 attempts] 

pdu reboot didn't help
Status: RESOLVED → REOPENED
Depends on: 960642
Resolution: FIXED → ---
SD card have been wiped and tegra have been flashed/re-imaged.
taking production jobs
Status: REOPENED → RESOLVED
Closed: 11 years ago10 years ago
Resolution: --- → FIXED
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.