Hi,
We are doing boot regression test using (in DB{410,820}c) an Android boot image that contains a ramdisk [1].
We aim to do functional testing in a way that if the basic testing fails the next test definition dosen't run, that's implies dependencies over -test entries in the job [2].
Does LAVA test shell provides this kind of functionality? If not, any idea to achieve this functionality.
Regards, Anibal
[1] https://validation.linaro.org/scheduler/job/1884978/definition [2] https://validation.linaro.org/scheduler/job/1884978/definition#defline117
On Wed, 4 Jul 2018, 19:26 Anibal Limon, anibal.limon@linaro.org wrote:
Hi,
We are doing boot regression test using (in DB{410,820}c) an Android boot image that contains a ramdisk [1].
We aim to do functional testing in a way that if the basic testing fails the next test definition dosen't run, that's implies dependencies over -test entries in the job [2].
Not dependencies as such - that would have to be handled inside the test shell scripts themselves.
However, if the basic testing can determine that the failure has occurred, that test shell needs to call lava-test-raise to end the test job without running any further test operations.
In the interests of portability, anything else needs to be handled by the test shell scripts.
See the examples of the AEP testing on staging.validation.linaro.org
Does LAVA test shell provides this kind of functionality? If not, any idea to achieve this functionality.
Regards, Anibal
[1] https://validation.linaro.org/scheduler/job/1884978/definition [2] https://validation.linaro.org/scheduler/job/1884978/definition#defline117 _______________________________________________ Lava-users mailing list Lava-users@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lava-users