On 06/30/2012 03:53 AM, Dave Pigott wrote:
Questions:
How does the test start running?
We really put that burden on Android (or some day Ubuntu). The "indicators" we create on the filesystem are supposed to instruct them what expect them to test. As per the mechanics of it all from LAVA, we'll just boot the board into the test image, and then wait for a timeout or a completion signal (via serial line) that the test is done.
Who initiates it, and how?
The test job JSON will tell LAVA via these new actions. We'll then set up the proper "indicators", boot to the test image, etc.
Over a serial connection that LAVA provides?
LAVA would now only communicate via serial to the test image, and the data we communicate will be pretty minimal.
Or as a process that gets auto run on bootup?
I think my other answers explain this, but it will be up to the test image itself to understand what it needs to do at start up.