Closed Bug 734321 (tegra-110) Opened 13 years ago Closed 10 years ago

tegra-110 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

ARM
Android
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

()

Details

(Whiteboard: [buildduty])

https://build.mozilla.org/buildapi/recent/tegra-110?numbuilds=100 - it was in fairly crappy shape, failing every two to five builds, until the morning of March 6th, when it went to pure red with slight accents of purple when it managed to get itself killed before it got itself killed for timing out.
I ran ./stop_cp on it but nothing else
Depends on: 734364
Summary: tegra-110 needs a disable and recover → tegra-110 problem tracking
Started after reimage.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
This board has not taken any jobs for 110 days. Adjusting the slave alloc note and re-opening this bug. tegra-110 108 days, 11:49:52 broken bm19-tests1-tegra 2012-03-08 22:02:55 0:07:16 4 bug 734321
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
it's a staging tegra and dashboard activity shows it has been online and available - if it's idle it's because of staging tegra master
Status: REOPENED → RESOLVED
Closed: 13 years ago12 years ago
Resolution: --- → FIXED
I will then remove it from production_config.py.
(In reply to Armen Zambrano G. [:armenzg] from comment #5) > I will then remove it from production_config.py. Never happened. ...its also actually sitting on a production foopy, (even though its pointing at staging buildbot) I'm touching up buildbot now and will start it targetted for production. If we need to decom/move it we should pull it off the production foopy. I did a PDU cycle, and it didn't seem to come back properly, lets reimage+sdcard swap and see where we end up
Status: RESOLVED → REOPENED
Depends on: 817995
Resolution: FIXED → ---
Tegra-110 re imaged and pingable + sd card swapped --- tegra-110.build.mtv1.mozilla.com ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
The last 3 times this tegra has attempted to run mochitest-7 on beta, it has hit bug 872076. Haven't seen that failure on any other machines.
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
Hasn't taken a job for 29 days.
Status: RESOLVED → REOPENED
QA Contact: armenzg → bugspam.Callek
Resolution: FIXED → ---
PDU reboot works, but can't even telnet into this tegra to see what's still wrong.
Depends on: 1016462
SD card replaced, reflashed, and reimaged. telnet tegra-110.tegra.releng.scl3.mozilla.com 20701 Trying 10.26.85.86... Connected to tegra-110.tegra.releng.scl3.mozilla.com. Escape character is '^]'. $>^] telnet> q
It apparently was enabled through that, and it's been rebooted several times since, but it hasn't taken a job.
Disabled in slavealloc to stop the pointless stream of reboots.
Depends on: 1028772
SD card formatted, tegra flashed and reimaged. vle@vle-10516 ~ $ telnet tegra-110.tegra.releng.scl3.mozilla.com 20701 Trying 10.26.85.86... Connected to tegra-110.tegra.releng.scl3.mozilla.com. Escape character is '^]'. $>^] telnet> q
Reenabled.
Status: REOPENED → RESOLVED
Closed: 11 years ago10 years ago
Resolution: --- → FIXED
Not actually taking jobs, though.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 1031509
replaced SD card, flashed and reimaged tegra. vle@vle-10516 ~ $ telnet tegra-110.tegra.releng.scl3.mozilla.com 20701 Trying 10.26.85.86... Connected to tegra-110.tegra.releng.scl3.mozilla.com. Escape character is '^]'. $>^] telnet> q
Let's pretend it'll work this time.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
foopy117 is going away, and these tegras are attached to it. They are being decomissioned in Bug 1043938, and I just disabled all of them in slavealloc and marked them as decom with a comment pointing at Bug 1043938
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.