Closed
Bug 770513
(tegra-218)
Opened 12 years ago
Closed 10 years ago
tegra-218 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Unassigned)
References
()
Details
(Whiteboard: [buildduty])
No description provided.
Comment 1•12 years ago
|
||
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
Comment 2•12 years ago
|
||
Last 49 jobs have been red or purple.
Reporter | ||
Comment 3•12 years ago
|
||
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Comment 4•12 years ago
|
||
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 → ---
Reporter | ||
Comment 5•12 years ago
|
||
ran stop_cp.sh on it.
Reporter | ||
Comment 6•12 years ago
|
||
Not sure what to do next. Callek?
Assignee: nobody → bugspam.Callek
Comment 7•12 years ago
|
||
Run stop_cp on it again? This time --with-fire?
Comment 8•12 years ago
|
||
(In reply to Phil Ringnalda (:philor) from comment #7) > Run stop_cp on it again? This time --with-fire? done
Comment 9•12 years ago
|
||
IT handled this, start_cp run now
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Comment 10•12 years ago
|
||
7 red in a row.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Summary: tegra-218 problem tracking → [disable me] tegra-218 problem tracking
Updated•12 years ago
|
Assignee: bugspam.Callek → nobody
Comment 11•12 years ago
|
||
haHa, https://secure.pub.build.mozilla.org/buildapi/recent/tegra-218
Comment 12•12 years ago
|
||
Ran stop_cp on it.
Summary: [disable me] tegra-218 problem tracking → tegra-218 problem tracking
Comment 13•12 years ago
|
||
[TODO Hand to recovery]
Reporter | ||
Comment 14•12 years ago
|
||
(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
Reporter | ||
Comment 15•12 years ago
|
||
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Comment 18•12 years ago
|
||
This is back to taking job(s) and is up now.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Comment 19•11 years ago
|
||
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 → ---
Comment 21•11 years ago
|
||
Successfully recovered.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Reporter | ||
Comment 23•10 years ago
|
||
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
Comment 24•10 years ago
|
||
SD card have been wiped and tegra have been flashed/re-imaged.
Comment 25•10 years ago
|
||
taking production jobs
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•