Closed Bug 767136 (tegra-011) Opened 12 years ago Closed 11 years ago

[staging] tegra-011 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

ARM
Android
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mattwoodrow, Unassigned)

References

()

Details

(Whiteboard: [buildduty][buildslave][loaner][mobile])

Attachments

(1 obsolete file)

Can I please get access to one of the android talos machines to debug 766059, this is blocking a q2 goal for layout.

Thanks!
Depends on: 767222
Attached patch [tools] update .json (obsolete) — Splinter Review
Just updating the .json here.

Loaning tegra-011 from staging.
Attachment #635546 - Flags: review?(bear)
:mattwoodrow

Once you get buildVPN access you should be able to use the tegra directly

Helpful Notes:
https://wiki.mozilla.org/ReleaseEngineering/How_To/Android_Tegras

You might want to setup a port forward through vpn1.releng.scl3.mozilla.com if you want to use your local shell.

FQDN of tegra is tegra-011.build.mtv1.mozilla.com

SUTAgent is commands can be issued over port 20701, and should have adb working on it as well.
Assignee: nobody → bugspam.Callek
Whiteboard: [buildduty][buildslave][loaner][mobile]
(In reply to Justin Wood (:Callek) from comment #1)
> Created attachment 635546 [details] [diff] [review]
> [tools] update .json
> 
> Just updating the .json here.
> 
> Loaning tegra-011 from staging.

in the past i've just renamed the tegra dir on the foopy and made an entry in slavealloc - the json file only really needs to change if it's a perma-loan
Comment on attachment 635546 [details] [diff] [review]
[tools] update .json

(In reply to Mike Taylor [:bear] from comment #3)
> in the past i've just renamed the tegra dir on the foopy and made an entry
> in slavealloc - the json file only really needs to change if it's a
> perma-loan

Deal, I was about to mark it in slavealloc anyway, but thats fine (I already moved the tegra dir to offline-*
Attachment #635546 - Attachment is obsolete: true
Attachment #635546 - Flags: review?(bear)
Matt, ping me if you need assistance running talos.  You can run it from your desktop, but you will need to use bm-remote as the webserver (just like tinderbox jobs do) as the tegra can reach that and not your host machine.
Matt, are you still using this loaner? Or should we claim it back?
No, I've finished with this for now, please take it back :)

Sorry for the delay in replying, been on PTO.
And thanks again for sorting this out so quickly, helped me a lot.
--> back to buildduty
Assignee: bugspam.Callek → nobody
Alias: tegra-011
Component: Release Engineering → Release Engineering: Machine Management
OS: Mac OS X → Android
QA Contact: armenzg
Hardware: x86 → ARM
Summary: loan an android talos machine to Matt Woodrow → tegra-011 problem tracking
Depends on: 776593
Depends on: 778170
back in staging
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
seems having issues with agent check, did a pdu reboot
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
and that worked, fixed
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Depends on: 913321
swapped sd card
Watcher version needs upgrading - upgrade unsuccessful via script, requesting this tegra to be reimaged with the new image that has the latest Watcher (1.16).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
No longer blocks: 925447
Depends on: 925447
Rebooted, and back in staging.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Summary: tegra-011 problem tracking → [staging] tegra-011 problem tracking
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.

Attachment

General

Created:
Updated:
Size: