Closed Bug 871710 (tegra-243) Opened 12 years ago Closed 11 years ago

tegra-243 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

ARM
Android

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: RyanVM, Unassigned)

References

()

Details

(Whiteboard: [buildduty][buildslaves][capacity])

https://tbpl.mozilla.org/php/getParsedLog.php?id=22902726&tree=Mozilla-Inbound Apparently it doesn't know what time it is. hwine is disabling in slavealloc.
plan is for :jmaher to confirm hardware clock functioning prior to sending for reimage
hmm, I am not sure how to access tegra-243, I was going to check the date, timezone via sutagent, then attempt to set it manually, verify it, reboot it, verify it.
I used to be able to log into build-vpn, then telnet tegra-243 and access it, now I don't seem to have access to that while on the buildVPN.
works for me: |telnet tegra-243.build.mozilla.org 20701| both from local machine while on buildVPN and from the build-vpn ssh jumphost
I get: telnet tegra-243.build.mozilla.org 20701 telnet: could not resolve tegra-243.build.mozilla.org/20701: System error (talos)jmaher@x230:~$ (talos)jmaher@x230:~$ ping tegra-243.build.mozilla.org ping: unknown host tegra-243.build.mozilla.org (talos)jmaher@x230:~$
(In reply to Joel Maher (:jmaher) from comment #5) > I get: > telnet tegra-243.build.mozilla.org 20701 > telnet: could not resolve tegra-243.build.mozilla.org/20701: System error > (talos)jmaher@x230:~$ > (talos)jmaher@x230:~$ ping tegra-243.build.mozilla.org > ping: unknown host tegra-243.build.mozilla.org > (talos)jmaher@x230:~$ These are resolver errors -- if you're connected to build VPN, your DNS resolver should include the search domain "build.mozilla.org". I bet it doesn't. That's the long term fix -- to get yourself going now, just use the IP address: $ host tegra-243 tegra-243.build.mozilla.org is an alias for tegra-243.build.mtv1.mozilla.com. tegra-243.build.mtv1.mozilla.com has address 10.250.51.83
thanks for the ip address, I was about to verify tzget and settime work as expected even across reboots. Callek, do we still do this in our sut_tools? did something change recently that hosed us?
Flags: needinfo?(bugspam.Callek)
(In reply to Joel Maher (:jmaher) from comment #7) > thanks for the ip address, I was about to verify tzget and settime work as > expected even across reboots. > > Callek, do we still do this in our sut_tools? did something change recently > that hosed us? We do it during installApp, *not* in verify. http://mxr.mozilla.org/build/source/tools/sut_tools/installApp.py#137
Flags: needinfo?(bugspam.Callek)
send it to the smelters.
needs reimaging per :jmaher
Blocks: 873168
Depends on: 873169
Alias: tegra-243
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
It's the only thing hitting bug 1017819, please recover/reflash/recard. Disabled in slavealloc.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
QA Contact: armenzg → bugspam.Callek
Depends on: 1031502
replaced SD card, flashed and reimaged tegra. vle@vle-10516 ~ $ telnet tegra-243.tegra.releng.scl3.mozilla.com 20701 Trying 10.26.85.191... Connected to tegra-243.tegra.releng.scl3.mozilla.com. Escape character is '^]'. $>^] telnet> q
Status: REOPENED → RESOLVED
Closed: 12 years ago11 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.