ReleaseEngineering/Archive/Android Tegras: Difference between revisions

Line 260: Line 260:
Unlike the N900's we don't run a buildbot environment on the device, but rather communicate to the device via the sutAgentAndroid program that the a-team maintains.  All of the buildslave activities are handled by the clientproxy.py program which monitors the Tegra and it's state and starts/stops the buildslave as needed.
Unlike the N900's we don't run a buildbot environment on the device, but rather communicate to the device via the sutAgentAndroid program that the a-team maintains.  All of the buildslave activities are handled by the clientproxy.py program which monitors the Tegra and it's state and starts/stops the buildslave as needed.


= References =
= Pandas =
 
== One source of truth ==
 
As of Oct 2012, [https://hg.mozilla.org/build/tools/file/default/buildfarm/mobile/devices.json <tt>tools/buildfarm/mobile/devices.json</tt>] should be the most authoritative document.
* if you find a tegra deployed that is not listed here, check [https://docs.google.com/spreadsheet/ccc?key=0AlIN8kWEeaF0dFJHSWN4WVNVZEhlREtUNWdTYnVtMlE&hl=en_US#gid=0 bear's master list]. If there, file a releng bug to get <tt>devices.json</tt> updated.
* if you find a PDU not labeled per the <tt>device.json</tt> file, file a releng bug to update the human labels.


== Determining what Pandas are attached to a Chassis ==
== Determining what Pandas are attached to a Chassis ==
Line 283: Line 277:


== Rebooting Pandas ==
== Rebooting Pandas ==
* Clone http://hg.mozilla.org/users/tmielczarek_mozilla.com/relay-control to get relay.py
* Clone http://hg.mozilla.org/users/tmielczarek_mozilla.com/relay-control to get relay.py
* Look in inventory for the panda you want to reboot, https://inventory.mozilla.org/en-US/#inventory, for example panda-0010: https://inventory.mozilla.org/en-US/systems/show/6812/
* Look in inventory for the panda you want to reboot, https://inventory.mozilla.org/en-US/#inventory, for example panda-0010: https://inventory.mozilla.org/en-US/systems/show/6812/
Line 293: Line 286:
* There's also a patch for create_dirs.sh queries the devices.json so you just have to specify the device name here https://bug807415.bugzilla.mozilla.org/attachment.cgi?id=683163
* There's also a patch for create_dirs.sh queries the devices.json so you just have to specify the device name here https://bug807415.bugzilla.mozilla.org/attachment.cgi?id=683163
** ie. python reboot_panda.py -f ~/hg/tools/buildfarm/mobile/devices.json -d panda-0873
** ie. python reboot_panda.py -f ~/hg/tools/buildfarm/mobile/devices.json -d panda-0873
= References =
== One source of truth ==
As of Oct 2012, [https://hg.mozilla.org/build/tools/file/default/buildfarm/mobile/devices.json <tt>tools/buildfarm/mobile/devices.json</tt>] should be the most authoritative document.
* if you find a tegra deployed that is not listed here, check [https://docs.google.com/spreadsheet/ccc?key=0AlIN8kWEeaF0dFJHSWN4WVNVZEhlREtUNWdTYnVtMlE&hl=en_US#gid=0 bear's master list]. If there, file a releng bug to get <tt>devices.json</tt> updated.
* if you find a PDU not labeled per the <tt>device.json</tt> file, file a releng bug to update the human labels.


= Tegra Dashboard =
= Tegra Dashboard =
canmove, Confirmed users
2,850

edits