Hi,
Chase did an excellent job and put together a piece of code that
allows us local execution of lava-test-shell. This means we can use
our 'lava' test definitions on the boards that are not deployed in any
LAB. There are 2 main reasons for doing that:
- prototyping tests for LAVA
- semi-automated execution of tests on targets that are not deployed in any LAB
Major part of this code is taken directly from lava dispatcher. There
are slight modifications but I would like to keep them to minimum or
remove at all (if possible). So the question follows - is there a way
to achieve the same goal with only LAVA code? One of the biggest
problems was requirement for ACKing that lava-test-shell requires.
This makes the tests 'interactive' which isn't best for semi-automated
execution. This bit was removed and now we're able to use test shell
locally in non-interactive mode. The README file describes the use
cases we're covering. Any comments are welcome. Code can be found
here:
https://git.linaro.org/qa/lava-local-test.git
milosz
Hi,
I'm having issues trying to set up a test that is multinode with lxc workers.
I end up with a test that fails with:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/lava_scheduler_app/dbutils.py", line 808, in select_device
pipeline_job.pipeline.validate_actions()
File "/usr/lib/python2.7/dist-packages/lava_dispatcher/pipeline/action.py", line 238, in validate_actions
raise JobError("Invalid job data: %s\n" % self.errors)
JobError: Invalid job data: ['Invalid job - missing protocol']
I have tried setting the lava-lxc protocol in a way that works with single node tests, but it doesn't seem to be there in the job for this specific node. Is there something I am missing with how to supply the lxc protocol for a role when using multinode?
Thanks,
Nick Huber
Hi,
I'm having issues where the test shell works and then it doesn't, even after resubmit of the same job that worked. In the Boot action, after the export PS1 = \"lava-test: # \" I get ". None" and stays there. Then tries to go to the lava-test-shell and hangs waiting for a prompt until it times out.
Any suggestions on this issue?
Below are the boot and test section logs:
- Boot: pastebin.ubuntu.com/23063162/
- Test: pastebin.ubuntu.com/23063161/
I will appreciate a response.
Thanks,
Josue
Hi,
Has anyone tried to set up a LAVA instance where another test management system invokes this instance just for test execution and return the results to the other test system?
In other words, using LAVA as a Test Execution Engine. Any pointers?
Thanks,
Josue
Hi,
Is there a way to override the constants or variables that are in the python code from the job definition or device dictionary? For example, the UBOOT_AUTOBOOT_PROMPT has the default value of 'Hit any key to stop autoboot' but my board displays 'Press SPACE to abort autoboot in 2 seconds'. Changing it in the code works but I was wondering if there is a more generic way of doing it. Perhaps a parameter I can send to the boot action from the job definition?
Thanks,
Josue
