Hello,
I see that YAML syntax for lava_test_shell has landed in linaro-dispatcher trunk, and that old JSON syntax is no longer (automagically) supported. I tried to do a straightforward conversion of http://people.linaro.org/~doanac/lava/lava_test_shell/testdefs/lava-test.jso... , but it throws exceptions trying to parse it. So, can you share examples of the new syntax?
Thanks, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
Paul Sokolovsky paul.sokolovsky@linaro.org writes:
Hello,
I see that YAML syntax for lava_test_shell has landed in linaro-dispatcher trunk, and that old JSON syntax is no longer (automagically) supported. I tried to do a straightforward conversion of http://people.linaro.org/~doanac/lava/lava_test_shell/testdefs/lava-test.jso... , but it throws exceptions trying to parse it. So, can you share examples of the new syntax?
Here is something I've been using:
metadata: format: Lava-Test Test Definition 1.0 name: streamline
run: steps: - "iface=$(ip route | awk '{ if ($1 == "default") { print($5) } }')" - "primary_ip=$(ip addr show "$iface" | awk '{ if ($1 == "inet") { gsub("/.*", "", $2); print($2) } }')" - "echo "<LAVA_SIGNAL_IP $primary_ip>"" - "lava-test-case pystone python -m test.pystone"
parse: pattern: "(?P<test_case_id>.*-*):\s+(?P<result>(pass|fail))"
These run steps are a bit silly for you I guess, but the syntax appears to work.
Cheers, mwh
On 11/08/2012 02:40 PM, Michael Hudson-Doyle wrote:
Paul Sokolovsky paul.sokolovsky@linaro.org writes:
Hello,
I see that YAML syntax for lava_test_shell has landed in linaro-dispatcher trunk, and that old JSON syntax is no longer (automagically) supported. I tried to do a straightforward conversion of http://people.linaro.org/~doanac/lava/lava_test_shell/testdefs/lava-test.jso... , but it throws exceptions trying to parse it. So, can you share examples of the new syntax?
Here is something I've been using:
metadata: format: Lava-Test Test Definition 1.0 name: streamline
run: steps: - "iface=$(ip route | awk '{ if ($1 == "default") { print($5) } }')" - "primary_ip=$(ip addr show "$iface" | awk '{ if ($1 == "inet") { gsub("/.*", "", $2); print($2) } }')" - "echo "<LAVA_SIGNAL_IP $primary_ip>"" - "lava-test-case pystone python -m test.pystone"
parse: pattern: "(?P<test_case_id>.*-*):\s+(?P<result>(pass|fail))"
This parse pattern may be a victim of copy paste. I don't think you have to escape the '' character in YAML, so I think its just a '\s+'
Andy Doan andy.doan@linaro.org writes:
parse: pattern: "(?P<test_case_id>.*-*):\s+(?P<result>(pass|fail))"
This parse pattern may be a victim of copy paste. I don't think you have to escape the '' character in YAML, so I think its just a '\s+'
Nope, it seems to be necessary. YAML is not without its odd bits :-)
Cheers, mwh
Hello,
On Fri, 09 Nov 2012 09:40:13 +1300 Michael Hudson-Doyle michael.hudson@linaro.org wrote:
Paul Sokolovsky paul.sokolovsky@linaro.org writes:
Hello,
I see that YAML syntax for lava_test_shell has landed in linaro-dispatcher trunk, and that old JSON syntax is no longer (automagically) supported. I tried to do a straightforward conversion of http://people.linaro.org/~doanac/lava/lava_test_shell/testdefs/lava-test.jso... , but it throws exceptions trying to parse it. So, can you share examples of the new syntax?
Here is something I've been using:
metadata: format: Lava-Test Test Definition 1.0 name: streamline
run: steps: - "iface=$(ip route | awk '{ if ($1 == "default") { print($5) } }')" - "primary_ip=$(ip addr show "$iface" | awk '{ if ($1 == "inet") { gsub("/.*", "", $2); print($2) } }')" - "echo "<LAVA_SIGNAL_IP $primary_ip>"" - "lava-test-case pystone python -m test.pystone"
parse: pattern: "(?P<test_case_id>.*-*):\s+(?P<result>(pass|fail))"
These run steps are a bit silly for you I guess, but the syntax appears to work.
Thanks, that worked for me. Just to clarify: is metadata::name is what used to be test_id in JSON format (re: http://people.linaro.org/~doanac/lava/lava_test_shell/testdefs/lava-test.jso... )?
And thanks for update the docs for new syntax. In that regard, how often are docs on http://lava.readthedocs.org/ updated? For example, http://lava-dispatcher.readthedocs.org/en/latest/ says it's "LAVA Dispatcher 0.6 documentation" which seems to be rather old wrt to latest release-0.21 tag in the bzr repo.
Cheers, mwh
Hi Paul,
On Monday 12 November 2012 04:01 PM, Paul Sokolovsky wrote:
Thanks, that worked for me. Just to clarify: is metadata::name is what used to be test_id in JSON format (re: http://people.linaro.org/~doanac/lava/lava_test_shell/testdefs/lava-test.jso... )?
Yes, you are right. "metadata: name == test_id"
Thank You.
On 11/12/2012 04:31 AM, Paul Sokolovsky wrote:
And thanks for update the docs for new syntax. In that regard, how often are docs onhttp://lava.readthedocs.org/ updated? For example, http://lava-dispatcher.readthedocs.org/en/latest/ says it's "LAVA Dispatcher 0.6 documentation" which seems to be rather old wrt to latest release-0.21 tag in the bzr repo.
We try to update it when we push changes to our /docs directory.
The old versioning you see is due to our sphinx configuration hard-coding the version. I'm trying to fix that now, but just note the contents are up-to-date.
On 11/12/2012 09:05 AM, Andy Doan wrote:
On 11/12/2012 04:31 AM, Paul Sokolovsky wrote:
And thanks for update the docs for new syntax. In that regard, how often are docs onhttp://lava.readthedocs.org/ updated? For example, http://lava-dispatcher.readthedocs.org/en/latest/ says it's "LAVA Dispatcher 0.6 documentation" which seems to be rather old wrt to latest release-0.21 tag in the bzr repo.
We try to update it when we push changes to our /docs directory.
The old versioning you see is due to our sphinx configuration hard-coding the version. I'm trying to fix that now, but just note the contents are up-to-date.
Ugh - My "fix" works locally but not on readthedocs.org. I've managed to break our documentation builds there:
https://readthedocs.org/builds/lava-dispatcher/325274/
Its complaining about missing versiontools. However, revno's 444 and 445 of the dispatcher added it in the same what that we have things for lp:lava-dashboard which builds correctly.
Any thoughts/suggestions/ideas are welcome.
Andy Doan andy.doan@linaro.org writes:
On 11/12/2012 09:05 AM, Andy Doan wrote:
On 11/12/2012 04:31 AM, Paul Sokolovsky wrote:
And thanks for update the docs for new syntax. In that regard, how often are docs onhttp://lava.readthedocs.org/ updated? For example, http://lava-dispatcher.readthedocs.org/en/latest/ says it's "LAVA Dispatcher 0.6 documentation" which seems to be rather old wrt to latest release-0.21 tag in the bzr repo.
We try to update it when we push changes to our /docs directory.
The old versioning you see is due to our sphinx configuration hard-coding the version. I'm trying to fix that now, but just note the contents are up-to-date.
Ugh - My "fix" works locally but not on readthedocs.org. I've managed to break our documentation builds there:
https://readthedocs.org/builds/lava-dispatcher/325274/
Its complaining about missing versiontools. However, revno's 444 and 445 of the dispatcher added it in the same what that we have things for lp:lava-dashboard which builds correctly.
Any thoughts/suggestions/ideas are welcome.
Is the "Use virtualenv: Install your project inside a virtualenv using setup.py install" checkbox checked in the project config?
Cheers, mwh
On 11/12/2012 01:59 PM, Michael Hudson-Doyle wrote:
Andy Doan andy.doan@linaro.org writes:
On 11/12/2012 09:05 AM, Andy Doan wrote:
On 11/12/2012 04:31 AM, Paul Sokolovsky wrote:
And thanks for update the docs for new syntax. In that regard, how often are docs onhttp://lava.readthedocs.org/ updated? For example, http://lava-dispatcher.readthedocs.org/en/latest/ says it's "LAVA Dispatcher 0.6 documentation" which seems to be rather old wrt to latest release-0.21 tag in the bzr repo.
We try to update it when we push changes to our /docs directory.
The old versioning you see is due to our sphinx configuration hard-coding the version. I'm trying to fix that now, but just note the contents are up-to-date.
Ugh - My "fix" works locally but not on readthedocs.org. I've managed to break our documentation builds there:
https://readthedocs.org/builds/lava-dispatcher/325274/
Its complaining about missing versiontools. However, revno's 444 and 445 of the dispatcher added it in the same what that we have things for lp:lava-dashboard which builds correctly.
Any thoughts/suggestions/ideas are welcome.
Is the "Use virtualenv: Install your project inside a virtualenv using setup.py install" checkbox checked in the project config?
That's probably the problem. Unfortunately I don't seem to have permissions to make such a change on the project. Can someone grant that to me? The creator was Spring, so we might have to get him to transfer ownership.
Andy Doan andy.doan@linaro.org writes:
On 11/12/2012 01:59 PM, Michael Hudson-Doyle wrote:
Andy Doan andy.doan@linaro.org writes:
On 11/12/2012 09:05 AM, Andy Doan wrote:
On 11/12/2012 04:31 AM, Paul Sokolovsky wrote:
And thanks for update the docs for new syntax. In that regard, how often are docs onhttp://lava.readthedocs.org/ updated? For example, http://lava-dispatcher.readthedocs.org/en/latest/ says it's "LAVA Dispatcher 0.6 documentation" which seems to be rather old wrt to latest release-0.21 tag in the bzr repo.
We try to update it when we push changes to our /docs directory.
The old versioning you see is due to our sphinx configuration hard-coding the version. I'm trying to fix that now, but just note the contents are up-to-date.
Ugh - My "fix" works locally but not on readthedocs.org. I've managed to break our documentation builds there:
https://readthedocs.org/builds/lava-dispatcher/325274/
Its complaining about missing versiontools. However, revno's 444 and 445 of the dispatcher added it in the same what that we have things for lp:lava-dashboard which builds correctly.
Any thoughts/suggestions/ideas are welcome.
Is the "Use virtualenv: Install your project inside a virtualenv using setup.py install" checkbox checked in the project config?
That's probably the problem. Unfortunately I don't seem to have permissions to make such a change on the project. Can someone grant that to me? The creator was Spring, so we might have to get him to transfer ownership.
Yeah, I was poking around at this. I couldn't see a way in the UI, and finally googling got me to https://github.com/rtfd/readthedocs.org/issues/203, which is a bit depressing really. Still, we should be able to hassle people on IRC into adding admins to the relevant projects -- maybe we should create a lava role user we can all log in as and get them to add that user to the various lava-* projects?
Cheers, mwh
On 11/14/2012 02:31 PM, Michael Hudson-Doyle wrote:
Andy Doan andy.doan@linaro.org writes:
On 11/12/2012 01:59 PM, Michael Hudson-Doyle wrote:
Andy Doan andy.doan@linaro.org writes:
On 11/12/2012 09:05 AM, Andy Doan wrote:
On 11/12/2012 04:31 AM, Paul Sokolovsky wrote:
And thanks for update the docs for new syntax. In that regard, how often are docs onhttp://lava.readthedocs.org/ updated? For example, http://lava-dispatcher.readthedocs.org/en/latest/ says it's "LAVA Dispatcher 0.6 documentation" which seems to be rather old wrt to latest release-0.21 tag in the bzr repo.
We try to update it when we push changes to our /docs directory.
The old versioning you see is due to our sphinx configuration hard-coding the version. I'm trying to fix that now, but just note the contents are up-to-date.
Ugh - My "fix" works locally but not on readthedocs.org. I've managed to break our documentation builds there:
https://readthedocs.org/builds/lava-dispatcher/325274/Its complaining about missing versiontools. However, revno's 444 and 445 of the dispatcher added it in the same what that we have things for lp:lava-dashboard which builds correctly.
Any thoughts/suggestions/ideas are welcome.
Is the "Use virtualenv: Install your project inside a virtualenv using setup.py install" checkbox checked in the project config?
That's probably the problem. Unfortunately I don't seem to have permissions to make such a change on the project. Can someone grant that to me? The creator was Spring, so we might have to get him to transfer ownership.
Yeah, I was poking around at this. I couldn't see a way in the UI, and finally googling got me to https://github.com/rtfd/readthedocs.org/issues/203, which is a bit depressing really. Still, we should be able to hassle people on IRC into adding admins to the relevant projects -- maybe we should create a lava role user we can all log in as and get them to add that user to the various lava-* projects?
Yep - shared account seems to be the only safe solution given this issue. Maybe we should create the shared account first and then pester the admins to change everything at one time?
Andy Doan andy.doan@linaro.org writes:
Yep - shared account seems to be the only safe solution given this issue. Maybe we should create the shared account first and then pester the admins to change everything at one time?
That's what I was thinking. Who wants to do it? :-)
Cheers, mwh
On 11/14/2012 06:33 PM, Michael Hudson-Doyle wrote:
Andy Doan andy.doan@linaro.org writes:
Yep - shared account seems to be the only safe solution given this issue. Maybe we should create the shared account first and then pester the admins to change everything at one time?
That's what I was thinking. Who wants to do it? :-)
This sounds like something I should do so that the smart guys working on my team can focus on hard stuff :).
linaro-validation@lists.linaro.org
-
Andy Doan -
Michael Hudson-Doyle -
Paul Sokolovsky -
Senthil Kumaran S