Closed
Bug 781781
(tegra-053)
Opened 12 years ago
Closed 10 years ago
tegra-053 problem tracking
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Unassigned)
References
()
Details
I can ping this, but cannot connect successfully to SUTAgent. It appears the SUTAgent will connect, but I don't get a prompt.
Comment 1•12 years ago
|
||
Just PDU Rebooted, will verify its up/ok -- if not will attach to generic recovery.
Alias: tegra-053
Summary: tegra-053 needs a PDU reboot → tegra-053 problem tracking
Comment 3•11 years ago
|
||
(fabric)[jwood@cruncher.srv.releng.scl3 fabric]$ python manage_foopies.py -f devices.json -j15 -D tegra-053 stat us stop tegra-053 - running - enabled - '' [foopy113.build.mozilla.org] run: echo "disable please" > ./disabled.flg [OK] Stopped tegra-053 RyanVM noticed that 3-of-last-4-reftest-runs failed with "application ran for longer than allowed maximum time" And no other devices hit that, :joel, :gbrown any ideas what we can/should look for in terms of "is this a bad board, needs a reimage, or what"
Status: RESOLVED → REOPENED
Flags: needinfo?(jmaher)
Flags: needinfo?(gbrown)
Resolution: FIXED → ---
Reporter | ||
Comment 4•11 years ago
|
||
I have no other ideas- 3/4 jobs is pretty telling. Reftests are a much longer and intensive run than most of the mochitest, talos and robocop. That might explain why we only see this on reftest.
Flags: needinfo?(jmaher)
Comment 5•11 years ago
|
||
Sorry - no ideas from me either. These device-specific failures are usually a mystery.
Flags: needinfo?(gbrown)
Updated•11 years ago
|
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Comment 6•11 years ago
|
||
Banking on a reimage recovering it. Once it is we'll need to re-enable it in slavealloc though.
Depends on: 918162
Comment 7•11 years ago
|
||
enabled in slavealloc
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Comment 9•11 years ago
|
||
flashed and reimaged
Comment 10•11 years ago
|
||
ping check failing, pdu reboot didn't help
Comment 11•10 years ago
|
||
handled in last recovery on Dec 16.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
Comment 12•10 years ago
|
||
decomming, per bug 949447.
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
•