Hi,
I'm trying to complete the docs for linaro test suites and add the way running local .yaml files on the remote server. From the lava-tool README I took the following line:
lava testdef submit
It kinda works:
milosz@milosz-nb:~/linaro/testcases/staging-test-definitions/openembedded$ lava testdef submit busybox.yaml
Creating job file... device_type: rtsm_fvp_base-aemv8a image: https://releases.linaro.org/13.09/openembedded/aarch64/vexpress64-openembedd...
Created job file 'lava-tool-job.json'.
Server connection parameters: server: https://mwasilew@validation.linaro.org/RPC2/ rpc_endpoint: RPC2
However I did something wrong as the connection wasn't successful. I got the following exception:
Traceback (most recent call last): File "/usr/local/bin/lava", line 9, in <module> load_entry_point('lava-tool==0.7.1', 'console_scripts', 'lava')() File "/usr/local/lib/python2.7/dist-packages/lava_tool-0.7.1-py2.7.egg/lava/tool/dispatcher.py", line 153, in run raise SystemExit(cls().dispatch(args)) File "/usr/local/lib/python2.7/dist-packages/lava_tool-0.7.1-py2.7.egg/lava/tool/dispatcher.py", line 143, in dispatch return command.invoke() File "/usr/local/lib/python2.7/dist-packages/lava_tool-0.7.1-py2.7.egg/lava/testdef/commands.py", line 101, in invoke super(submit, self).submit(job_file) File "/usr/local/lib/python2.7/dist-packages/lava_tool-0.7.1-py2.7.egg/lava/helper/command.py", line 113, in submit job_id = server.scheduler.submit_job(jobdata) File "/usr/lib/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib/python2.7/xmlrpclib.py", line 1578, in __request verbose=self.__verbose File "/usr/local/lib/python2.7/dist-packages/lava_tool-0.7.1-py2.7.egg/lava_tool/authtoken.py", line 77, in request response = self._opener.open(request) File "/usr/lib/python2.7/urllib2.py", line 400, in open response = self._open(req, data) File "/usr/lib/python2.7/urllib2.py", line 418, in _open '_open', req) File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain result = func(*args) File "/usr/lib/python2.7/urllib2.py", line 1215, in https_open return self.do_open(httplib.HTTPSConnection, req) File "/usr/lib/python2.7/urllib2.py", line 1177, in do_open raise URLError(err) urllib2.URLError: <urlopen error [Errno 110] Connection timed out>
Is there any docs I can check to make it working?
milosz
On Fri, Nov 08, 2013 at 11:22:44AM +0000, Milosz Wasilewski wrote:
Hi,
I'm trying to complete the docs for linaro test suites and add the way running local .yaml files on the remote server. From the lava-tool README I took the following line:
lava testdef submit
It kinda works:
milosz@milosz-nb:~/linaro/testcases/staging-test-definitions/openembedded$ lava testdef submit busybox.yaml
Creating job file... device_type: rtsm_fvp_base-aemv8a image: https://releases.linaro.org/13.09/openembedded/aarch64/vexpress64-openembedd...
Created job file 'lava-tool-job.json'.
Server connection parameters: server: https://mwasilew@validation.linaro.org/RPC2/ rpc_endpoint: RPC2
you want: server: <any name you want> rpc_endpoint: https://mwasilew@validation.linaro.org/RPC2/
I recognize this UI is not optimal and will appreciate any suggestions on how to improve. Adding an explanation next to each parameter would probably help.
On 8 November 2013 14:21, Antonio Terceiro antonio.terceiro@linaro.org wrote:
On Fri, Nov 08, 2013 at 11:22:44AM +0000, Milosz Wasilewski wrote:
Hi,
I'm trying to complete the docs for linaro test suites and add the way running local .yaml files on the remote server. From the lava-tool README I took the following line:
lava testdef submit
It kinda works:
milosz@milosz-nb:~/linaro/testcases/staging-test-definitions/openembedded$ lava testdef submit busybox.yaml
Creating job file... device_type: rtsm_fvp_base-aemv8a image: https://releases.linaro.org/13.09/openembedded/aarch64/vexpress64-openembedd...
Created job file 'lava-tool-job.json'.
Server connection parameters: server: https://mwasilew@validation.linaro.org/RPC2/ rpc_endpoint: RPC2
you want: server: <any name you want> rpc_endpoint: https://mwasilew@validation.linaro.org/RPC2/
I recognize this UI is not optimal and will appreciate any suggestions on how to improve. Adding an explanation next to each parameter would probably help.
is the server parameter used in any way? If not it might be just removed. Another problem I noticed when I managed to submit the job is missing submit_results command (in the result JSON file). I guess this is by design, but adding it might be a good idea.
milosz
On Fri, Nov 08, 2013 at 03:58:40PM +0000, Milosz Wasilewski wrote:
On 8 November 2013 14:21, Antonio Terceiro antonio.terceiro@linaro.org wrote:
I recognize this UI is not optimal and will appreciate any suggestions on how to improve. Adding an explanation next to each parameter would probably help.
is the server parameter used in any way? If not it might be just removed.
it is used to suggest the URL for you next time. So say you have submitted to `myserver` at http://example.com/RPC2/, next time it will prompt you with `myserver` as default, and when you just hit ENTER, it will also suggest the URL associated with `myserver` for you so you just have to hit ENTER again if that's OK. So if you use more than one server we can choose between then just by name, and the URL will be given to you.
Another problem I noticed when I managed to submit the job is missing submit_results command (in the result JSON file). I guess this is by design, but adding it might be a good idea.
Yes, that is by design because submitting results assumes you know to which bundle stream you want to submit to which we don't. Maybe we can add a new parameter for that.
On 8 November 2013 20:42, Antonio Terceiro antonio.terceiro@linaro.org wrote:
On Fri, Nov 08, 2013 at 03:58:40PM +0000, Milosz Wasilewski wrote:
On 8 November 2013 14:21, Antonio Terceiro antonio.terceiro@linaro.org wrote:
I recognize this UI is not optimal and will appreciate any suggestions on how to improve. Adding an explanation next to each parameter would probably help.
is the server parameter used in any way? If not it might be just removed.
it is used to suggest the URL for you next time. So say you have submitted to `myserver` at http://example.com/RPC2/, next time it will prompt you with `myserver` as default, and when you just hit ENTER, it will also suggest the URL associated with `myserver` for you so you just have to hit ENTER again if that's OK. So if you use more than one server we can choose between then just by name, and the URL will be given to you.
IMO using just the RPC endpoint here would be better. I tend to forget what URL 'myserver' is set to. It would also remove the ambiguity I run into when trying this for the first time.
Another problem I noticed when I managed to submit the job is missing submit_results command (in the result JSON file). I guess this is by design, but adding it might be a good idea.
Yes, that is by design because submitting results assumes you know to which bundle stream you want to submit to which we don't. Maybe we can add a new parameter for that.
I would consider that as a wish list rather than a strong requirement. I consider using lava-tool for submitting jobs more as a sandbox than a production like method. On the other hand it would be pretty useful to test result parsing as well.
-- milosz
-- Antonio Terceiro Software Engineer - Linaro http://www.linaro.org
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
linaro-validation@lists.linaro.org
-
Antonio Terceiro -
Milosz Wasilewski