Hello lava users,
I have to deal with a board with a very limited storage size. Overall capacity is 64 MB, with about 30 MB remaining.
This is a clear limitation for Lava usage. Hence my questions:
* Is there a possibility to configure Lava tests installation on an external storage, such as an USB drive?
* In Lava recent versions, is it possible to optimize the overlay tests structure?
* Today, assuming that tests are stored in a git repo, for each test the complete repo is copied in each overlay
* A balance has to be made between one git containing all the tests and one git per test (extreme configurations)
* Is there a better way to manage this? In a ideal world, that would mean copy only what is needed and not more
Thanks, have a nice day
Does that mean that a lava-docker-worker is designed to only run jobs which use "docker"?
I would not like to modify all my legacy jobs which do not use the new "docker" thing. Also, I understood that this new "docker" in LAVA jobs was mainly aimed at Android testing.
For Linux/yocto, that sounds like useless extra complexity (unless I miss something).
From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of Milosz Wasilewski
Sent: Thursday, October 29, 2020 11:03 AM
To: Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com>
Cc: lava-users(a)lists.lavasoftware.org <lava-users(a)lavasoftware.org>
Subject: [EXT] Re: [Lava-users] lava-docker-worker: how to customize?
Caution: EXT Email
On Thu, 29 Oct 2020 at 10:00, Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> wrote:
> Hi All,
> I was exploring the new lava-docker-worker released with 2020.09.
> It is pretty handy to start a slave, but I am wondering how to customize the slave image:
> I need to add inside my own tools (like uuu), config files (like ser2net.conf), and also install additional packages.
> How do you do this on your side?
I think you're confusing 2 things here. The lava-docker-worker image is not supposed to run the jobs. For that you use 'docker: <image
name>: in the job definition actions. This is the image that should
contain flashing tools like uuu.
As for ser2net I'm not sure what is the recommendation (Antonio, could you comment?). We're stil using host based ser2net.
> Finally, I noticed that if I don't do a "service tftpd-hpa restart", TFTP does not work. Is it a known issue?
> Philippe Mazet
> Lava-users mailing list
Lava-users mailing list
I was exploring the new lava-docker-worker released with 2020.09.
It is pretty handy to start a slave, but I am wondering how to customize the slave image:
I need to add inside my own tools (like uuu), config files (like ser2net.conf), and also install additional packages.
How do you do this on your side?
Finally, I noticed that if I don't do a "service tftpd-hpa restart", TFTP does not work. Is it a known issue?
Hi Lava users,
I am getting " Job error: Invalid job data: ['Unable to connect to shell - missing connections block.'] " error while submitting jobs which is using 'uuu' deploy and boot method.
Same job I am using in a different server and there it is working perfectly. Both the servers are using same version.
Please check the attached job yaml file (uuu-job.yaml) and the job log (uuu-job-fail-log.txt).
For the same job, I may got 'complete'(for most case) and
'incomplete' in lava server dashboard, the logs are almost the same and
both show that the job finished correctly and the result is pass.
My question is: how is the server define the job as 'incomplete'?
When I check the lava server log, I got the same error log for ALL
'complete' and 'incomplete' jobs(most of them are actually mark as
complete in the dashboard result):
2020-10-10 09:40:58,386 DEBUG - rv1126-evb
2020-10-10 09:40:58,395 DEBUG -> rv1126-evb-01 (Idle, Unknown)
2020-10-10 09:40:58,395 DEBUG |-->  scheduling
2020-10-10 09:40:58,486 INFO  START => lava-slave247
2020-10-10 09:40:58,517 INFO  lava-slave247 => START_OK
2020-10-10 09:41:09,539 DEBUG lava-logs => PING(20)
2020-10-10 09:41:13,537 INFO  lava-slave247 => END (lava-run
crashed, mark job as INCOMPLETE)
2020-10-10 09:41:13,759 ERROR  Unable to dump 'description.yaml'
2020-10-10 09:41:13,759 ERROR  Compressed data ended before
the end-of-stream marker was reached
Traceback (most recent call last):
line 312, in _handle_end
description = lzma.decompress(compressed_description)
File "/usr/lib/python3.5/lzma.py", line 340, in decompress
raise LZMAError("Compressed data ended before the "
_lzma.LZMAError: Compressed data ended before the end-of-stream marker
2020-10-10 09:41:13,763 DEBUG lava-slave241 => PING(20)
How can I link the Requirement page (any web page) URL to LAVA test cases ?
1. I just want to see that web page URL in test case results page log after
execution of test.
Do I need to add that web page URL as metadata data in while writing the
I guess we may need to include under "metadata:" in yaml file, right? is
my understanding correct?
so that we can see the same in "Details" section under the corresponding
Job. (Ex: https://staging.validation.linaro.org/scheduler/job/280173 .
Attached the screen shot)
Testcase ID : TestCase_ID: xxxxx
Requirement Path: Requirement_URL_Page : XXXXX
On Mon, 19 Oct 2020 at 15:05, koti koti via groups.io <kotisoftwaretest=
> How can I link the Requirement page (any web page) URL to LAVA test cases ?
> 1. I just want to see that web page URL in test case results page log after
> execution of test.
> Do I need to add that web page URL as metadata data in while writing the
> test definitions?
> Groups.io Links: You receive all messages sent to this group.
> View/Reply Online (#964): https://groups.io/g/kernelci/message/964
> Mute This Topic: https://groups.io/mt/77654665/4395798
> Group Owner: kernelci+owner(a)groups.io
> Unsubscribe: https://groups.io/g/kernelci/unsub [
I have connected my Dragonboard-845 DUT to Lava Dispatcher (Dispatcher is
"raspberry pi 4" SBC)
Now I need to set up "Remote Power Control" and "Set target into Program
Please can someone let me know the required hardware list like "Remote
PDU (Remote Power Distribution)" and "Relays" units purchase URL's in
India for below requirement.
1. Power ON/Power OFF/reboot the target from Lava Dispatcher. ( Hope this
functionality may be fully filled by the PDU. Can some let me know low cost
PDU's URLs with 2 outlets)
2. set target into Programing mode ( to flash the images) (Is this
functionality can be done by any relays? if yes, Please can someone let me
know the available relays URL's in India)
1. I have found a couple of Relays URL's (
* But these are not available in India.*