tegra-201 got itself into a bad state this morning, and now it either gets a 660480 "killed by signal 15" or makes it into updateSUT.py and tries to get 1.08 but goes into a socket disconnected/reconnecting spiral until it gives up there. Those are both quick enough ways to fail that it's chewing through quite a few jobs.

taken offline and needs to be moved to staging

It came back up recently, and has been passing >80% of its jobs as green, so leaving it up for now. We *can* move it to staging still if we want though.

seems have problems Connection refused - working on it

and its back 01/31/2013 05:44:01: INFO: tegra-201 p online active active :: 2013-01-31 05:44:01,751 tegra-201 p online active active :: bash-3.2$ ps auxw | grep "tegra-201" cltbld 52163 0.0 0.1 2482972 11792 ?? S 5:42am 0:00.73 /opt/local/Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python /opt/local/bin/twistd --no_save --rundir=/builds/tegra-201 --pidfile=/builds/tegra-201/twistd.pid --python=/builds/tegra-201/buildbot.tac cltbld 55303 0.0 0.0 2446812 2784 ?? S 10Dec12 7:57.55 /opt/local/Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python clientproxy.py -b --device=tegra-201 cltbld 55302 0.0 0.1 2475240 5500 ?? S 10Dec12 1:42.21 /opt/local/Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Contents/MacOS/Python clientproxy.py -b --device=tegra-201 cltbld 52257 0.0 0.0 2435492 352 s003 U+ 5:44am 0:00.00 grep tegra-201

Disabled due to issue with its foopy (foopy24) tracked in bug 839375

Back in production.