561908 - Tracking bug for Android unittest/talos infrastructure

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Aki Sasaki (not active)]

Using the model I diagrammed for Bear in Toronto --

buildbot master <-> linux box with multiple buildbot slaves

buildbot slave <-> heartbeat monitor <-> SUT agent on Tegra/phone running Android

We want to investigate local webservers.  I had partial integration of buildbot and SUT without the heartbeat monitor, but never fully got that running with the heartbeat monitor.

We need builds and devices and an SUT agent, and Bear will need devices shipped to him for local testing and development.

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

Please contact me with any questions related to actually running the tests and getting results (once you have the hardware).  I might be of some help for buildbot stuff, but that is not my expertise

Comment 2

[Bob Moss :bmoss]

I thought we were going to work out the "plumbing" with WinMo so that we didn't have any blockage and then when we get the Android gear and s/w together we would do a swap. Did this change? In any case, when the tegra2 boards arrive I will make sure that some of them get to bear.

Comment 3

[Aki Sasaki (not active)]

I spent a decent chunk of time trying to unbrick the Acers (none of the 5 seem to be working now) -- I requisitioned a Windows 7 netbook, and tried installing the hacked bits onto the three un-flashed phones, and tried installing the un-hacked bits onto the two previously flashed phones.

Then I thought about switching to the Touch Pros which Just Work... but which have an older version of the agent.  After a while it looked like testing on Winmo was going to have a higher overhead than just testing the integration pieces.

Then 1.0.1 and 1.1 release work took priority, and joduinn told me to hand off all Android work to Bear, including this task specifically, though he seemed surprised when I repeated that to him yesterday. =\

If it's any consolation, we already had buildbot talking to the SUT agent on the Touch Pros and running Ts previously; the only piece we hadn't integrated was the heartbeat monitor, which I don't foresee as being a big issue (assuming the devices aren't bricked).

Comment 4

[Joel Maher ( :jmaher ) (UTC -8)]

I know the pain.  Actually to help me develop, I have a python agent which I wrote for testing on linux desktop (and n900!)  This has allowed me to run tests end to end just like we would on winmo.  You can get the agent here:
http://people.mozilla.org/~jmaher/test-agent.py
 * this doesn't have the heartbeat or log channel, just the plain telnet interface

It would be nice to have the majority of the integration work resolved before having android builds stable enough to test on.

Comment 5

[Aki Sasaki (not active)]

Thanks Joel!

... I think the heartbeat is specifically what we want to test for here, though.

Comment 6

[Aki Sasaki (not active)]

Tracking bug with 0 open bugs. Resolved.