Hey,
We're using lava to test multiple of our devices.
While most tests are similar ("does the device still have a working ethernet connection"), some slightly differ. For example a device might have LEDs 1-3, another the LEDs 1-5.
Today I save multiple test shell definitions test1-device1.yaml, test1-device2.yaml, ..., which all just differ by providing "device1", "device2", ... in an argument to the actual test script, so the run: section looks like this:
run:
steps:
- cd ./testdir/
- ./run_test.py device1
I would like to get rid of the two, separate .yaml files and only have a `./run_test.py ${device}` or similar. Is there any way to provide a variable from the job definition to the test shell definition?
Or are things like the device type set in the environment so I could access them?
Best regards, Olli
Dear,
I wonder if it is possible on the job page, I could quickly find other
guys' jobs with a search function? I tried next, but returned nothing.
owner_query=hedy.lamarr
Thanks,
Hedy Lamarr
Dear all,
I don't know what operation I have done, but when a device does not have
any running job, I still see the device is in running status.
I just saw this 1 time, maybe it's a bug or just bad luck.
Anyway, I can't reproduce it on other devices, so it's ok.
But, could you teach me to reset the status to make the device work again?
Do we have some method to reset the status from "Running" to "Idle", or any
api if we don't have an interface on the UI?
[image: image.png]
Thanks,
Hedy Lamarr
Dear,
Recently I'm learning and evaluating LAVA to see if it can help us.
I saw next from
https://validation.linaro.org/static/docs/v2/connections.html:
{% set connection_list = ['uart0', 'uart1'] %}{% set
connection_commands = {'uart0': 'telnet dispatcher01 7001', 'uart1':
'telnet dispatcher01 7002'} %}
I'm pretty confused by the 'uart0', 'uart1'. Should I explicitly specify
something in my job to let some action to choose 'uart0' or 'uart1'? How
does LAVA know at which time it should choose which uart?
Thanks,
Hedy Lamarr
Hello everyone,
I'm new to LAVA and I have some issue with 'iso-installer' for ubuntu 20.04
. As you know, in ubuntu 20.04 the preseed file would not use
'debian_installer' and use 'subiquity' instead, Also LAVA does not support
'subiquity' for 'iso-installer', so I don't know how can I use
'iso-installer' for testing my ubuntu 20.04.
Dear,
I saw https://lkft.linaro.org/ by chance, I wonder if we could benefit from
this on our android test? Does it already have any kernel test for android
kernel?
Thanks,
Hedy Lamarr