On 12 Jun 2012, at 21:51, Alexander Sack wrote: > On Wed, Jun 6, 2012 at 4:22 AM, YongQin Liu <[email protected]> wrote: >> >> >> On 6 June 2012 10:11, Zach Pfeffer <[email protected]> wrote: >>> >>> On 5 June 2012 21:08, YongQin Liu <[email protected]> wrote: >>>> Hi, all >>>> >>>> Some information: >>>> >>>> 1. the boot time is about 2 minutes. >>>> tested with panda stable build. >>>> >>>> 2. the specification of timeout for each test is doing via this bp: >>>> >>>> >>>> >>>> https://blueprints.launchpad.net/lava-dispatcher/+spec/timeout-for-android-test-actions >>>> when this BP is completed, the timeout option is assumed that can be >>>> specified for each test >>>> in LAVA_TEST_PLAN and each test of LAVA_TEST_X and each test of >>>> MONKEY_RUNNER_URL_X >>>> >>>> Hi, Zach >>>> >>>> | If glmark2 hangs, reboot the unit and restart on 0xbench. >>>> >>>> Do you mean reboot just when glmark2 timeout, or reboot when any test >>>> timeout? >>> >>> Reboot when any test times out and start the next test in the list if >>> there is one. >>> >> OK, I see, thanks. >> >>> >>>> And, If the android hangs at some test, lava should be able to reboot >>>> the >>>> image and continue the next test now. >>> >>> This is working now? >> >> Yes, lava will reboot the android image before do any test action if the >> android hangs or has no response or is not on android image session. >> > > With this already available it feels like it should be super easy to > just reboot in between all test suites? ... what's the effort? I would > really like to give that a try. It definitely would be much cleaner > and as I explained before it would also ensure that test suite always > get started while system is in a pristine "fresh boot" state. >
It seems to me that it should be trivial to add "command": "boot-linaro-android-image" to the json file between each test? Dave _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
