canmove, Confirmed users
1,126
edits
ReleaseEngineering/Archive/Android Tegras: Difference between revisions
ReleaseEngineering/Archive/Android Tegras (view source)
Revision as of 15:53, 5 May 2012
, 5 May 2012→Environment: Fix link to http://developer.nvidia.com/tegra-250-tango-development-kits
(→Environment: Fix link to http://developer.nvidia.com/tegra-250-tango-development-kits) |
|||
| Line 266: | Line 266: | ||
* All of the sut related helper code is found '''/builds/sut_tools''' (a symlink to /builds/tools/sut_tools/) | * All of the sut related helper code is found '''/builds/sut_tools''' (a symlink to /builds/tools/sut_tools/) | ||
Tegra is the short name for the Tegra 250 Developer Kit test board, see http://developer.nvidia.com | Tegra is the short name for the Tegra 250 Developer Kit test board, see http://developer.nvidia.com/tegra-250-tango-development-kits for details. It allows us to install and test Firefox on a device that runs Android Froyo while also allowing for debugging. | ||
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. | ||