Botao Sun <[email protected]> writes: > Hi Michael, > > In the last 2 days I'm trying to write some test case definition files but > I'm confused about the format. I have made some experiments and here is my > observation: > > I use Panda ES as an example, and the YAML file looks like this: > > metadata: > format: Lava-Test Test Definition 1.0 > name: botao-panda-es-ubuntu-test > > run: > steps: > - lava-test-case botao-panda-es-ubuntu-test-uname --shell echo > "This is a test" || true > - lava-test-case botao-panda-es-ubuntu-test-uname --shell uname -a > true > - lava-test-case botao-panda-es-ubuntu-test-uname --shell "ifconfig > -a" || true
Firstly, is there a reason you're using the lava-test-case helper? If you can use the "output test results in an easy to parse" form, it's a bit easier to work on. > Then the second line will be failed to run by an index error: > > - lava-test-case botao-panda-es-ubuntu-test-uname --shell uname -a true It will? Can you post a link to a job that shows this? > The first and the third line can be executed successfully. The "|| true" > will let the command line to return a "true" value whatever its status. I don't think that's necessary any more. It was for a while, but not in the latest release. > But on the LAVA wikipage it says: > > The second form is indicated by the –shell argument, for example: > > run: > steps: > - "lava-test-case fail-test --shell false" > - "lava-test-case pass-test --shell true" > > Then if I write like the example shows, it will fail to run. So do we need > to update that wiki example or is there something wrong in my understanding? I think you might be using an out of date version of the code. Cheers, mwh _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
