User:Bear:AndroidTegraNotes

Tegra 250 Android Setup

Notes on how I setup the buildbot environment to enable using the Tegra 250 for Reference and Talos testing.

Assumptions

• Assumes Buildbot v0.8.+
• Tegra 250 series board with 2.1 Android or better
• Linux server to run proxy, buildbot slaves and other tools
• Linux server to run simple web server to serve Talos and other resources needed

Buildbot Master

The buildbot master was configured to use a "stock" Mozilla-test master

Buildbot Slave server

Because each Tegra can connect to the network using ethernet, that is the primary method of communicating with it. The micro USB is only used to install new versions of the SUTAgentAndroid tool and for debugging.

Also because the tests are running on the Tegra, we can run multiple buildbot slaves on a single Linux server.

Slave Server Layout

• tegra-???/ -- one each per buildslave
• sut_tools/ -- from HG: build/tools/sut/
  • cleanup.py
  • reboot.py
  • installApp.py
  • devicemanager.py
• talos-data/
  • talos/ created via hg
• clientproxy.py
• tegras.txt - text file with one entry per line for each active buildslave/tegra pair

clientproxy.py

Assumes Python 2.6 environment

python clientproxy.py [-d|--debug] [-p|--bbpath] [-t|--tegras]
   -d enable debug output
   -p buildslave base directory. defaults to ./
   -t list of Tegra devices to manage. defaults to ./tegras.txt

tegras.txt

Sample file

tegra-001 192.168.1.1
tegra-002 192.168.1.2
tegra-042 192.168.1.39

Note: the first field is the directory name, clientproxy.py assumes relative to the value specified via the -t option

test web server

The tests that run on the Tegra for Reference and Talos tests all need to pull data from a webserver. This can be any Nginx/Apache web server with the following files in the root directory.

• getInfo.html - symlink to talos/getInfo.html
• startup_test - symlink to talos/startup_test
• page_load_test - symlink to talos/page_load_test
• talos - symlink to talos/ checkout