User:Bear:AndroidTegraNotes: Difference between revisions

m
 
Line 43: Line 43:
     -p buildslave base directory. defaults to ./
     -p buildslave base directory. defaults to ./
     -t list of Tegra devices to manage. defaults to ./tegras.txt
     -t list of Tegra devices to manage. defaults to ./tegras.txt
Testing clientproxy:
* Setup at least 2 or more tegras
* Start clientproxy.py --echo
** ensure buildslaves have started for the tegras
* Edit tegras.txt to comment out one of the tegras
* Save the file and check, buildslave should be removed for that tegra
* Edit tegras.txt and re-enable tegra
* Save the file and check, buildslave should be started
* Sendchange to start some tests, look to make sure both buildslaves are active
** during the test run you should see each tegra's output with two reboot notices but only the second one will restart the buildslave. The first one will show "proxy.flg found - looping monitor" in it's output:
INFO    android-tegra01: listening for heartbeat
ERROR  android-tegra01: socket timeout while monitoring
INFO    android-tegra01: hbActive False bbActive True
INFO    android-tegra01: proxy.flg found - looping monitor
INFO    android-tegra01: listening for heartbeat
INFO    android-tegra01: socket data [20090103-06:23:34 trace output]
INFO    android-tegra01: heartbeat detected
** during a test run, unplug a tegra from the network and make sure the monitor timesout the heartbeat and shuts down the buildslave
** during a test run, connect with adb shell and kill the sutAgent - make sure monitor notices the socket has died and shuts down the buildslave
* manually clear the /sdcard/tests dir using '''adb shell''' and also use '''adb uninstall org.mozilla.fennec''' and then trigger a build to make sure the cleanup and install steps work
** after the run, '''cd /data/data/org.mozilla.fennec''' and ensure that application.ini is the same as the apk that was installed


==== tegras.txt ====
==== tegras.txt ====
470

edits