I feel stopping and rebooting and continuing with the next test is what we want to aim for.
On this front I wonder if we should directly go for rebooting for _all_ tests to ensure that every test gets executed the same runtime environment.
Big benefit is obviously that tests can then stop services, change runtime state etc. as much as they like without bothering about bringing the system back into a clean state.
Would that be hard? Why wouldn't we do this?
On Tue, Jun 5, 2012 at 4:18 AM, YongQin Liu yongqin.liu@linaro.org wrote:
Hi, Zach
Could you help to give some comment about the mail below?
Thanks, Yongqin Liu
On 28 May 2012 15:29, YongQin Liu yongqin.liu@linaro.org wrote:
Hi, Zach
I am now working on a bp that adding the timeout process for android test action in lava. I am not sure if we should reboot the android image when the test run for a time longer than expected. so I'd like to know your opinion which you want to do. a. stop the test and restart the android image, then continue the next test b. stop the test and continue the next test c. others
Like we submit a job to lava for running "monkey,glmark2,0xbench" test on android, while glmark2 test runs for a longer time than expected(like in which case if we don't stop it it will run for ever).
In this case which one would you like? reboot the android and continue the next 0xbench test, or just stopped the glmark2 test and continue to run the next 0xbench test?
Thanks, Yongqin Liu
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation