lava-dispatch test.json --target panda01
made in this way: { "job_name": "foo", "target": "panda01", "timeout": 18000, "actions": [ { "command": "lava_test_shell", "parameters": { "timeout": 1800, "testdef_urls": ["file:///home/novello/ae/test/lava/test-definitions/openembedded/etherner.yaml"] } } ] } Then I see thei ERROR Target includes no deployment_data:::: What does it means . Best regards The ethernet.yaml file is made in this way: metadata: name: ethernet format: "Lava-Test-Shell Test Definition 1.0" description: "Test network in OE."
install: git-repos: - git://git.linaro.org/qa/test-definitions.git
run: steps: - "cd test-definitions/openembedded/scripts" - "./ethernet.sh"
parse: pattern: "^(?P<test_case_id>[a-zA-Z0-9_-]+):\s(?P<result>\w+)" fixupdict: PASS: pass FAIL: fail
The path is correct because from explorrer I can open it.
emb)root@hp:/home/novello/ae/test/lava/lava-dispatcher/doc# ~ bash: /root: È una directory (emb)root@hp:/home/novello/ae/test/lava/lava-dispatcher/doc# lava-dispatch test1.json --target panda01 <LAVA_DISPATCHER>2013-05-28 10:53:44 AM INFO: Attempting to connect to device Connected. <LAVA_DISPATCHER>2013-05-28 10:53:44 AM INFO: Matched 'Connected\.\r' which means all-good <LAVA_DISPATCHER>2013-05-28 10:53:44 AM INFO: [ACTION-B] lava_test_shell is started with {u'testdef_urls': [u'file:///home/novello/ae/test/lava/test-definitions/openembedded/etherner.yaml'], u'timeout': 1800} <LAVA_DISPATCHER>2013-05-28 10:53:44 AM WARNING: [ACTION-E] lava_test_shell is finished with error (Target includes no deployment_data). Lava failed at action lava_test_shell with error:Target includes no deployment_data Traceback (most recent call last): File "/srv/lava/.cache/branch-cache/lava-dispatcher/checkouts/563-tyler.baker@linaro.org-20130219062639-8ooe0nuv759tv1ls/lava_dispatcher/job.py", line 177, in run action.run(**params) File "/srv/lava/.cache/branch-cache/lava-dispatcher/checkouts/563-tyler.baker@linaro.org-20130219062639-8ooe0nuv759tv1ls/lava_dispatcher/actions/lava_test_shell.py", line 486, in run self._assert_target(target) File "/srv/lava/.cache/branch-cache/lava-dispatcher/checkouts/563-tyler.baker@linaro.org-20130219062639-8ooe0nuv759tv1ls/lava_dispatcher/actions/lava_test_shell.py", line 626, in _assert_target raise RuntimeError('Target includes no deployment_data') RuntimeError: Target includes no deployment_data Then I seee this error:
Traceback (most recent call last): File "/srv/lava/instances/emb/code/r115/bin/lava", line 61, in <module> lava.tool.main.LavaDispatcher.run() File "/srv/lava/.cache/eggs/lava_tool-0.6-py2.7.egg/lava/tool/dispatcher.py", line 147, in run raise SystemExit(cls().dispatch(args)) File "/srv/lava/.cache/eggs/lava_tool-0.6-py2.7.egg/lava/tool/dispatcher.py", line 137, in dispatch return command.invoke() File "/srv/lava/.cache/branch-cache/lava-dispatcher/checkouts/563-tyler.baker@linaro.org-20130219062639-8ooe0nuv759tv1ls/lava/dispatcher/commands.py", line 129, in invoke job.run() File "/srv/lava/.cache/branch-cache/lava-dispatcher/checkouts/563-tyler.baker@linaro.org-20130219062639-8ooe0nuv759tv1ls/lava_dispatcher/job.py", line 177, in run action.run(**params) File "/srv/lava/.cache/branch-cache/lava-dispatcher/checkouts/563-tyler.baker@linaro.org-20130219062639-8ooe0nuv759tv1ls/lava_dispatcher/actions/lava_test_shell.py", line 486, in run self._assert_target(target) File "/srv/lava/.cache/branch-cache/lava-dispatcher/checkouts/563-tyler.baker@linaro.org-20130219062639-8ooe0nuv759tv1ls/lava_dispatcher/actions/lava_test_shell.py", line 626, in _assert_target raise RuntimeError('Target includes no deployment_data') RuntimeError: Target includes no deployment_data
BEST REGARDS NOVELLO G.
On 28 May 2013 10:07, Novello Giampiero novellogp64@gmail.com wrote:
"testdef_urls":["file:///home/novello/ae/test/lava/test-definitions/openembedded/etherner.yaml"] }
hmm, looks like a typing mistake. Did you fix that in your setup and the problem persist?
Best Regards, milosz
Hi Novello,
On Tuesday 28 May 2013 02:37 PM, Novello Giampiero wrote:
lava-dispatch test.json --target panda01
made in this way: { "job_name": "foo", "target": "panda01", "timeout": 18000, "actions": [ { "command": "lava_test_shell", "parameters": { "timeout": 1800, "testdef_urls": ["file:///home/novello/ae/test/lava/test-definitions/openembedded/etherner.yaml"] } } ] } Then I see thei ERROR Target includes no deployment_data:::: What does it means .
You are missing a 'deploy_linaro_image' action which is mandatory to know what image you want to deploy and then run the above test. Please have a look at the following simple job file for what are the actions you are missing in your job file:
http://staging.validation.linaro.org/scheduler/job/44581/definition
Thank You.
Ok there was a typing mistake . But the mai problem is that I don't want to 'deploy_linaro_image' because i woulkd like to test a buildroot make file system? There are some other possibilities ?
P.s.: I have already installed in the target the lava-test.
Thank you e best regards Novello G.
2013/5/28 Senthil Kumaran senthil.kumaran@linaro.org
Hi Novello,
On Tuesday 28 May 2013 02:37 PM, Novello Giampiero wrote:
lava-dispatch test.json --target panda01
made in this way: { "job_name": "foo", "target": "panda01", "timeout": 18000, "actions": [ { "command": "lava_test_shell", "parameters": { "timeout": 1800, "testdef_urls": ["file:///home/novello/ae/**test/lava/test-definitions/** openembedded/etherner.yaml"] } } ] } Then I see thei ERROR Target includes no deployment_data:::: What does it means .
You are missing a 'deploy_linaro_image' action which is mandatory to know what image you want to deploy and then run the above test. Please have a look at the following simple job file for what are the actions you are missing in your job file:
http://staging.validation.**linaro.org/scheduler/job/**44581/definitionhttp://staging.validation.linaro.org/scheduler/job/44581/definition
Thank You.
Senthil Kumaran http://www.stylesen.org/ http://www.sasenthilkumaran.**com/ http://www.sasenthilkumaran.com/
______________________________**_________________ linaro-validation mailing list linaro-validation@lists.**linaro.org linaro-validation@lists.linaro.org http://lists.linaro.org/**mailman/listinfo/linaro-**validationhttp://lists.linaro.org/mailman/listinfo/linaro-validation
Hi Novello,
On Tuesday 28 May 2013 06:26 PM, Novello Giampiero wrote:
But the mai problem is that I don't want to 'deploy_linaro_image' because i woulkd like to test a buildroot make file system? There are some other possibilities ?
You can also try out dummy_deploy.
Thank You.
On Tue, May 28, 2013 at 11:28:08PM +0530, Senthil Kumaran S wrote:
Hi Novello,
On Tuesday 28 May 2013 06:26 PM, Novello Giampiero wrote:
But the mai problem is that I don't want to 'deploy_linaro_image' because i woulkd like to test a buildroot make file system? There are some other possibilities ?
You can also try out dummy_deploy.
I don't think that is documented at all :-(
Basically you need an action like this:
{ "command": "dummy_deploy", "parameters": { "type": "ubuntu" } },
where type can be "ubuntu", "android", or "oe". "oe" can be used for most standard-ish GNU/Linux rootfs since it assumes very little about the contents of the rootfs.
linaro-validation@lists.linaro.org
-
Antonio Terceiro -
Milosz Wasilewski -
Novello Giampiero -
Senthil Kumaran