Closed
Bug 731629
(tegra-284)
Opened 13 years ago
Closed 10 years ago
tegra-284 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Unassigned)
References
()
Details
(Whiteboard: [buildduty][buildslave][tegra])
https://build.mozilla.org/buildapi/recent/tegra-284?numbuilds=125 - outside the regular pattern of alternating between exception and retry, it has spent the past week alternating between a dozen red 1200 second timeouts and one exception.
Updated•13 years ago
|
Priority: -- → P3
Comment 1•13 years ago
|
||
tegra-284 has been disabled
Updated•13 years ago
|
Alias: tegra-284
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: release → armenzg
Summary: Please disable tegra-284 and enroll it in tegra recovery → tegra-284 problem tracking
Comment 2•13 years ago
|
||
back in production
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 3•12 years ago
|
||
Had to PDU cycle twice, but its up and taking a job now. Took a Looooong while to escape a hung SUTAgent connection.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 12 years ago
Resolution: --- → FIXED
Comment 4•12 years ago
|
||
Disabled due to issue with its foopy (foopy24) tracked in bug 839375
Comment 5•12 years ago
|
||
Back in production.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Comment 6•11 years ago
|
||
Thursday, October 31, 2013 11:32:15 PM
Comment 7•11 years ago
|
||
SD card has been replaced and reimaged/flashed.
Comment 8•11 years ago
|
||
tegra is recoverd and sd card is reformatted.
host-7-26:~ johnPech$ telnet tegra-284.build.mtv1.mozilla.com 20701
Trying 10.250.51.124...
Connected to tegra-284.build.mtv1.mozilla.com.
Escape character is '^]'.
$>
Comment 9•11 years ago
|
||
handled in last recovery on Dec 16.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Comment 10•11 years ago
|
||
2014-01-16 10:40:20 tegra-284 p OFFLINE active OFFLINE :: PING tegra-284.tegra.releng.scl3.mozilla.com (10.26.85.232) 56(84) bytes of data. From foopy128.tegra.releng.scl3.mozilla.com (10.26.84.27) icmp_seq=1 Destination Host Unreachable;error.flg [Automation Error: Unable to ping device after 5 attempts]
pdu reboot didn't help
Comment 11•11 years ago
|
||
SD Card have been wiped and Tegra have been flashed.
Comment 12•11 years ago
|
||
taking production jobs
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 13•10 years ago
|
||
Hasn't taken a job for 7 days.
Status: RESOLVED → REOPENED
QA Contact: armenzg → bugspam.Callek
Resolution: FIXED → ---
Reporter | ||
Comment 14•10 years ago
|
||
Disabled in slavealloc to stop the stream of pointless reboots.
Comment 15•10 years ago
|
||
SD card formatted, tegra flashed and reimaged.
vle@vle-10516 ~ $ telnet tegra-284.tegra.releng.scl3.mozilla.com 20701
Trying 10.26.85.232...
Connected to tegra-284.tegra.releng.scl3.mozilla.com.
Escape character is '^]'.
$>^]
telnet> q
Reporter | ||
Comment 16•10 years ago
|
||
Reenabled.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 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
•