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
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
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. 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?
Thanks.
Best Regards Botao Sun
Botao Sun botao.sun@linaro.org 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
Hi Michael,
I don't have specific reason to use lava-test-case, I just want to give it try and familiar with the whole process. For the form "output test results in an easy to parse" you mentioned, would you send me a documentation link about it?
For the index error, here is the output log:
http://validation.linaro.org/lava-server/dashboard/attachment/229774/view
http://validation.linaro.org/lava-server/dashboard/attachment/229749/view
For the source code I'm using, I installed LAVA by following these steps:
1. Add linaro-maintainers ppa; 2. apt-get update; 3. apt-get install
Is it the correct way?
Thank you.
Best Regards Botao Sun
On Mon, Jan 28, 2013 at 9:30 AM, Michael Hudson-Doyle < michael.hudson@linaro.org> wrote:
Botao Sun botao.sun@linaro.org 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
Botao Sun botao.sun@linaro.org writes:
Hi Michael,
I don't have specific reason to use lava-test-case, I just want to give it try and familiar with the whole process.
Fair enough.
For the form "output test results in an easy to parse" you mentioned, would you send me a documentation link about it?
Only http://lava-dispatcher.readthedocs.org/en/latest/lava_test_shell.html unfortunately.
For the index error, here is the output log:
http://validation.linaro.org/lava-server/dashboard/attachment/229774/view
http://validation.linaro.org/lava-server/dashboard/attachment/229749/view
Oh. Ah, I think I see the problem -- yaml sucks basically. Try this instead:
run: steps: - 'lava-test-case botao-panda-es-ubuntu-test-test --shell echo "This is a test"' - 'lava-test-case botao-panda-es-ubuntu-test-uname --shell uname -a' - 'lava-test-case botao-panda-es-ubuntu-test-ifconfig --shell ifconfig -a'
For the source code I'm using, I installed LAVA by following these steps:
- Add linaro-maintainers ppa;
- apt-get update;
- apt-get install
Is it the correct way?
I no longer suspect you of running old code :-)
Cheers, mwh
Thank you.
Best Regards Botao Sun
On Mon, Jan 28, 2013 at 9:30 AM, Michael Hudson-Doyle < michael.hudson@linaro.org> wrote:
Botao Sun botao.sun@linaro.org 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
Ha, yes, after changed format to yours, it works well!
http://validation.linaro.org/lava-server/dashboard/attachment/232202/view
Thank you!
Best Regards Botao Sun
On Mon, Jan 28, 2013 at 5:43 PM, Michael Hudson-Doyle < michael.hudson@linaro.org> wrote:
Botao Sun botao.sun@linaro.org writes:
Hi Michael,
I don't have specific reason to use lava-test-case, I just want to give
it
try and familiar with the whole process.
Fair enough.
For the form "output test results in an easy to parse" you mentioned, would you send me a documentation link about it?
Only http://lava-dispatcher.readthedocs.org/en/latest/lava_test_shell.html unfortunately.
For the index error, here is the output log:
http://validation.linaro.org/lava-server/dashboard/attachment/229774/view
http://validation.linaro.org/lava-server/dashboard/attachment/229749/view
Oh. Ah, I think I see the problem -- yaml sucks basically. Try this instead:
run: steps: - 'lava-test-case botao-panda-es-ubuntu-test-test --shell echo "This is a test"' - 'lava-test-case botao-panda-es-ubuntu-test-uname --shell uname -a' - 'lava-test-case botao-panda-es-ubuntu-test-ifconfig --shell ifconfig -a'
For the source code I'm using, I installed LAVA by following these steps:
- Add linaro-maintainers ppa;
- apt-get update;
- apt-get install
Is it the correct way?
I no longer suspect you of running old code :-)
Cheers, mwh
Thank you.
Best Regards Botao Sun
On Mon, Jan 28, 2013 at 9:30 AM, Michael Hudson-Doyle < michael.hudson@linaro.org> wrote:
Botao Sun botao.sun@linaro.org 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
On Sun, Jan 27, 2013 at 4:28 AM, Botao Sun botao.sun@linaro.org wrote:
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
the command above is not proper shell ... its bogus to type uname -a true on the command line ... not sure why you think that the documentation suggest doing that..
- lava-test-case botao-panda-es-ubuntu-test-uname --shell "ifconfig-a" || true
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
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. 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"
those commands are fine and are proper shell commands... "uname -a true" however is not correct shell ...
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?
Thanks.
Best Regards Botao Sun
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
Hi Alexander,
At the beginning I wrote "uname -a true" because on the wikipage:
http://lava-dispatcher.readthedocs.org/en/latest/lava_test_shell.html
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"
So After "--shell", I add my command line "uname -a". then add "true" at the end. And in my case, "pass-test" is replaced to "botao-panda-es-ubuntu-test-uname". That's why I finally wrote command like this:
- lava-test-case botao-panda-es-ubuntu-test-uname --shell uname -a true
And it doesn't work.
On Mon, Jan 28, 2013 at 8:45 PM, Alexander Sack asac@linaro.org wrote:
On Sun, Jan 27, 2013 at 4:28 AM, Botao Sun botao.sun@linaro.org wrote:
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
the command above is not proper shell ... its bogus to type uname -a true on the command line ... not sure why you think that the documentation suggest doing that..
- lava-test-case botao-panda-es-ubuntu-test-uname --shell"ifconfig
-a" || true
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
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.
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"
those commands are fine and are proper shell commands... "uname -a true" however is not correct shell ...
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?
Thanks.
Best Regards Botao Sun
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
-- Alexander Sack Director, Linaro Platform Engineering http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-validation@lists.linaro.org
-
Alexander Sack -
Botao Sun -
Michael Hudson-Doyle