- lava-users - op-lists.linaro.org

by Denis HUMEAU

After getting stats on my setup robustness, the step forward is have a complete view on the lava errors we meet in incomplete jobs. >From what I see in incomplete jobs, my intention is to query on test suite lava and the name "job". In the query builder, if I use test suite as condition model, I can't use the job field name. Do you have any advice on how to proceed? Denis

7 years, 1 month

3
5
0 0

adb device lost during cts/vts

by Axel Lebourhis

Hi all, I'm facing a pretty frustrating issue when running CTS/VTS with LAVA. I'm using Linaro's tradefed test definition : https://git.linaro.org/qa/test-definitions.git/tree/automated/android/trade… During some runs, the adb connection is lost, leading to incomplete test job. Do you know if this behavior is known and mostly general ? Or is it a bad configuration on my side ? Maybe someone knows some way to keep a reliable adb connection to the target ? Best regards, Axel

7 years, 1 month

3
3
0 0

What's the difference of lava log feedback & log output on the web page?

by Larry Shen

Sometimes, I can see the lava log feedback to repeat the the lava log output, sometimes cannot. Could you give an example simple inline test, so I can always see some log feedback? Something like: - test: timeout: minutes: 1 definitions: - from: inline name: smoke-case path: inline/test.yaml repository: metadata: format: Lava-Test Test Definition 1.0 name: smoke-case-run description: Run smoke case run: steps: - lava-test-case "Case_001" --shell 'echo "Case001 gstreamer ok";' How could I let ` Case001 gstreamer ok` also been seen in feedback log level?

7 years, 1 month

2
1
0 0

lava-test-case only handles lower case results strings

by Patryk Mungai Ndungu

Hello, I have recently upgraded from 2018.11 to 2019.03 and have noticed that the results of a lot of the tests I have been running no longer got parsed correctly by LAVA. This was because I was sending the results using upper case results strings. Eg. lava-test-case <test-case> PASS opposed to lava-test-case <test-case> pass This resulted in the following logs in the lava job: Received signal: <TESTCASE> TEST_CASE_ID=ETH_T_001 RESULT=PASS Bad test result: PASS Changing my results parsing script to only send lower case results strings fixed the issue, but was this restriction intended with the upgrade? Kind Regards, Patryk

7 years, 1 month

3
6
0 0

password change prompt: how to automate?

by Diego Russo

Hello, I have a system that as soon as LAVA logins, it requires the password to be changed (the password needs to be typed twice). Is there an easy way to automate it using LAVA? Cheers -- Diego Russo | Staff Software Engineer | Mbed Linux OS ARM Ltd. CPC1, Capital Park, Cambridge Road, Fulbourn, CB21 5XE, United Kingdom http://www.diegor.co.uk - https://os.mbed.com/linux-os/ IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

7 years, 1 month

2
3
0 0

Error: "deploy stage is missing" in multinode job

by Axel Lebourhis

Hi all, I'm currently trying to make a multinode job for CTS on Android 9. During this job, I need to unlock uboot so I use the "interactive" test action. But when I add it to my job definition, I get an error message during the run : "Nothing to run. Maybe the 'deploy' stage is missing, otherwise this is a bug which should be reported." If I remove the test action with the "interactive" method, I won't get that error. Maybe I'm missing something but I don't get what it could be. You will find attached a test job example which leads to this error. Best regards, Axel

7 years, 1 month

2
4
0 0

timeouts for deploy vs http-download

by Kevin Hilman

Hello, I'm trying to customize the http-download timeout as documented[1], but I doesn't seem to work. The global deploy time always seems to win. Based on the doc, I did this, I added the following to my job[2] timeouts: actions: http-download: minutes: 15 However, in the job output, you can see that the http-download timeout value is set to 25 min (1500 sec) which is coming from the deploy action timeout. I got the same result when tryin to use timeouts: connections: What am I missing? Kevin [1] https://validation.linaro.org/static/docs/v2/timeouts.html?highlight=http_d… [2] https://lava.automotivelinux.org/scheduler/job/3270/definition#defline44 [3] https://lava.automotivelinux.org/scheduler/job/3270#action_1-1-1

7 years, 1 month

4
8
0 0

Re: [Lava-users] Why make the decision to limit job context in lava master?

by Larry Shen

Thanks, Remi, So, looking forward to your patch which allow admins to extend the white list with a variable in the settings. Regards, Larry From: Remi Duraffort <remi.duraffort(a)linaro.org> Sent: Thursday, May 23, 2019 3:59 PM To: Larry Shen <larry.shen(a)nxp.com> Cc: lava-users(a)lists.lavasoftware.org Subject: [EXT] Re: [Lava-users] Why make the decision to limit job context in lava master? Caution: EXT Email Hello Larry, 1. We mainly have 2 kinds of situations: a) Something like "uboot_ums_flash" which already in linaro lava tree. In the past, this can be overridden by job context. And I guess a lots of other variables which spread every corner of different jinja2 files. Huge I think, I really worried how lava can add so many keys in whitelist... Why do you have to update uboot_ums_flash in the job definition and not in the device dictionary? This sounds more like a device specific information instead of a job definition one. Anyway, having a long list of keys in the white list is not really a problem. This is only a python array, nothing more. b) Something which just used in device jinja2 to control some different command in different situations. I know linaro accept upstreams for device-type, I have no idea if private lab's device jinja2 also useful for other people. Contributions are welcome. A rule of thumb for device-type integration/templates is often: is the device available for purchase by someone outside your company? If yes, then it's a good idea to upstream it. If not, then it's more a case-by-case decision. 2. Sounds you guys will not rollback this commit because security issue. So two suggestions: Sorry no :( a) I don't know how this security issue could impact for an internal lab which not exposed to external internet. Anyway, if possible to add a configure to any settings to let admin to decide if we care this security issue? More details to come later on, but I don't think this is a good idea. b) If a) not easy to do or not accept, if possible this whitelist be stored in database or other persist file, so user can free to add his own keyword to whitelist, then even we will upgrade lava to later new version, we can still remain the keyword setting in the past, meanwhile user still can free to add any keyword to whitelist without upstream again and again for this hard coded whitelist, I don't think this make sense. I'm currently writing down a patch to allow admins to extend the white list with a variable in the settings. Please consider. BTW, as Tim Jaacks said in other thread: this limit not happen in multinode job, is it a bug, so next release we will also have this backdoor closed? I'm fixing this second issue in https://git.lavasoftware.org/lava/lava/merge_requests/547<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavas…> Thanks for reporting it. Rgds -- Rémi Duraffort LAVA Team, Linaro

7 years, 2 months

2
1
0 0

auto_login and minimal boot

by Diego Russo

Hello, In my job definition I have a minimal boot: https://staging.validation.linaro.org/static/docs/v2/actions-boot.html?high… Documentation says "auto-login and transfer_overlay are both supported for this method." But if I add auto_login the schema validation in the submit page will raise a warning: "Valid definition with warnings: extra keys not allowed @ data['actions']['boot']['minimal']" Of course if I take the auto_login out, the validation is green. If I leave the auto_login, it will be used. I think the validation needs to reflect what documentation says. Cheers -- Diego Russo | Staff Software Engineer | Mbed Linux OS ARM Ltd. CPC1, Capital Park, Cambridge Road, Fulbourn, CB21 5XE, United Kingdom http://www.diegor.co.uk - https://os.mbed.com/linux-os/ IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

7 years, 2 months

2
2
0 0

Re: [Lava-users] Why make the decision to limit job context in lava master?

by Larry Shen

Thanks, Remi, 1. We mainly have 2 kinds of situations: a) Something like "uboot_ums_flash" which already in linaro lava tree. In the past, this can be overridden by job context. And I guess a lots of other variables which spread every corner of different jinja2 files. Huge I think, I really worried how lava can add so many keys in whitelist... b) Something which just used in device jinja2 to control some different command in different situations. I know linaro accept upstreams for device-type, I have no idea if private lab's device jinja2 also useful for other people. 2. Sounds you guys will not rollback this commit because security issue. So two suggestions: a) I don't know how this security issue could impact for an internal lab which not exposed to external internet. Anyway, if possible to add a configure to any settings to let admin to decide if we care this security issue? b) If a) not easy to do or not accept, if possible this whitelist be stored in database or other persist file, so user can free to add his own keyword to whitelist, then even we will upgrade lava to later new version, we can still remain the keyword setting in the past, meanwhile user still can free to add any keyword to whitelist without upstream again and again for this hard coded whitelist, I don't think this make sense. Please consider. BTW, as Tim Jaacks said in other thread: this limit not happen in multinode job, is it a bug, so next release we will also have this backdoor closed? Regards, Larry -----Original Message----- From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of lava-users-request(a)lists.lavasoftware.org Sent: Tuesday, May 21, 2019 11:13 PM To: lava-users(a)lists.lavasoftware.org Subject: [EXT] Lava-users Digest, Vol 9, Issue 19 Caution: EXT Email Send Lava-users mailing list submissions to lava-users(a)lists.lavasoftware.org To subscribe or unsubscribe via the World Wide Web, visit https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lav… or, via email, send a message with subject or body 'help' to lava-users-request(a)lists.lavasoftware.org You can reach the person managing the list at lava-users-owner(a)lists.lavasoftware.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Lava-users digest..." Today's Topics: 1. Re: Why make the decision to limit job context in lava master? (Remi Duraffort) 2. Re: timeouts for deploy vs http-download (Remi Duraffort) 3. Re: Using transfer overlay (Pete Dyer) ---------------------------------------------------------------------- Message: 1 Date: Tue, 21 May 2019 17:02:35 +0200 From: Remi Duraffort <remi.duraffort(a)linaro.org> To: lava-users <lava-users(a)lists.lavasoftware.org> Subject: Re: [Lava-users] Why make the decision to limit job context in lava master? Message-ID: <CANJfhHeXiuVi02dMfmzeQ5EjnP=SqDymDNoyfwDB2XNN8ckodg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello, we had to enforce the content of the context dictionary in order to fix a security issue that we found recently. The full details of the security issue will be disclosed when a CVE is available. We know that this is annoying for many people so we tried to collect all the valid use cases before the previous release. Which variables are you setting in the context? Is the corresponding code upstreamed? Cheers Le lun. 20 mai 2019 à 10:49, cnspring2002 <cnspring2002(a)aliyun.com> a écrit : > +1, we also have same issue, had to pending new version deploy. > > Message: 1 > Date: Mon, 20 May 2019 05:39:40 +0000 > From: Larry Shen <larry.shen(a)nxp.com> > To: "lava-users(a)lists.lavasoftware.org" > <lava-users(a)lists.lavasoftware.org> > Subject: [Lava-users] Why make the decision to limit job context in > lava master? > Message-ID: > < > DBBPR04MB63291E1DC4F5F202DEDFE16699060(a)DBBPR04MB6329.eurprd04.prod.out > look.com > > > > Content-Type: text/plain; charset="utf-8" > > For 2019.04 version, we see next: > > Job context > ----------- > > > The schema validator is now checking the content of the `context` dictionary. Only the following keys are now allowed: > > > * `arch`, `boot_console`, `boot_root`, `cpu`, `extra_options`, > `guestfs_driveid`, `guestfs_interface`, `guestfs_size`, `machine`, > `memory`, `model`, `monitor`, `netdevice`, `serial`, `vga` > > * `bootloader_prompt`, `console_device`, `extra_kernel_args`, > `extra_nfsroot_args`, `kernel_loglevel`, `kernel_start_message`, > `lava_test_results_dir`, `menu_interrupt_prompt`, `mustang_menu_list`, > `test_character_delay`, `tftp_mac_address` > > Jobs using keys that are not listed in this list will be rejected. > > > We usually set an customized context in job, and in device-type jinja2, use this context to just different value to set proper parameters. > After this limit, all things break! > > So, my question is: > > > lava could be designed to as a framework to give freedom to users to do their things as in the past, why we now enhance so many limits to users? > And additional, and workaround for my scenario? > > Regards, > Larry > > > > > _______________________________________________ > Lava-users mailing list > Lava-users(a)lists.lavasoftware.org > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist > s.lavasoftware.org%2Fmailman%2Flistinfo%2Flava-users&data=02%7C01% > 7Clarry.shen%40nxp.com%7C2ebbb071596f41c8816208d6ddfee338%7C686ea1d3bc > 2b4c6fa92cd99c5c301635%7C0%7C0%7C636940484145033600&sdata=cpnWI8y6 > NzawoUy%2BOtunqchIyXsaHO0ryYzPyJf3Gw0%3D&reserved=0 -- Rémi Duraffort LAVA Team, Linaro

7 years, 2 months

2
1
0 0

Using transfer overlay

by Pete Dyer

Hello, I'm using transfer overlay to get a set of tests onto the target. However I want to untar it into /scratch instead of / because of storage requirements. This I can do quite easily. However the tests are going to try to run from / (e.g. /lava-10473/bin/lava-test-runner /lava-10473/1) Is there a way of running tests from /scratch/lava-10473.... ? Or a way of defining a command to run immediately after the transfer overlay that makes a link between /lava-10473 and /scratch/lava-10473 ? Thanks. Pete IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

7 years, 2 months

4
7
0 0

Re: [Lava-users] Why make the decision to limit job context in lava master?

by cnspring2002

+1, we also have same issue, had to pending new version deploy. Message: 1 Date: Mon, 20 May 2019 05:39:40 +0000 From: Larry Shen <larry.shen(a)nxp.com> To: "lava-users(a)lists.lavasoftware.org" <lava-users(a)lists.lavasoftware.org> Subject: [Lava-users] Why make the decision to limit job context in lava master? Message-ID: <DBBPR04MB63291E1DC4F5F202DEDFE16699060(a)DBBPR04MB6329.eurprd04.prod.outlook.com> Content-Type: text/plain; charset="utf-8" For 2019.04 version, we see next: Job context ----------- The schema validator is now checking the content of the `context` dictionary. Only the following keys are now allowed: * `arch`, `boot_console`, `boot_root`, `cpu`, `extra_options`, `guestfs_driveid`, `guestfs_interface`, `guestfs_size`, `machine`, `memory`, `model`, `monitor`, `netdevice`, `serial`, `vga` * `bootloader_prompt`, `console_device`, `extra_kernel_args`, `extra_nfsroot_args`, `kernel_loglevel`, `kernel_start_message`, `lava_test_results_dir`, `menu_interrupt_prompt`, `mustang_menu_list`, `test_character_delay`, `tftp_mac_address` Jobs using keys that are not listed in this list will be rejected. We usually set an customized context in job, and in device-type jinja2, use this context to just different value to set proper parameters. After this limit, all things break! So, my question is: lava could be designed to as a framework to give freedom to users to do their things as in the past, why we now enhance so many limits to users? And additional, and workaround for my scenario? Regards, Larry

7 years, 2 months

2
1
0 0

Problems with email notifications

by Frank, Matthias

Hi lava-users, my Debian machine running lava-server (2019.04) sends mails via msmtp/msmtp-mta. Mails from cron or apt work fine. But I got no mails from lava. Even when I submit a test job with a notify statement. notify: criteria: status: finished recipients: - to: method: email user: default verbosity: verbose The user default uses my real mail address not a system mail address. This is the Django log: INFO 2019-05-10 07:18:15,546 notifications [1343] sending email notification to XXXXXXX(a)YYYYYY.com ERROR 2019-05-10 07:18:15,557 notifications [Errno 99] Cannot assign requested address Traceback (most recent call last): File "/usr/lib/python3/dist-packages/lava_scheduler_app/notifications.py", line 303, in send_notifications title, body, settings.SERVER_EMAIL, [recipient.email_address] File "/usr/lib/python3/dist-packages/django/core/mail/__init__.py", line 62, in send_mail return mail.send() File "/usr/lib/python3/dist-packages/django/core/mail/message.py", line 348, in send return self.get_connection(fail_silently).send_messages([self]) File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 104, in send_messages new_conn_created = self.open() File "/usr/lib/python3/dist-packages/django/core/mail/backends/smtp.py", line 64, in open self.connection = self.connection_class(self.host, self.port, **connection_params) File "/usr/lib/python3.5/smtplib.py", line 251, in __init__ (code, msg) = self.connect(host, port) File "/usr/lib/python3.5/smtplib.py", line 335, in connect self.sock = self._get_socket(host, port, self.timeout) File "/usr/lib/python3.5/smtplib.py", line 306, in _get_socket self.source_address) File "/usr/lib/python3.5/socket.py", line 712, in create_connection raise err File "/usr/lib/python3.5/socket.py", line 703, in create_connection sock.connect(sa) OSError: [Errno 99] Cannot assign requested address WARNING 2019-05-10 07:18:15,558 notifications [1343] failed to send email notification to XXXXXXX(a)YYYYYY.com Lava has a problem with smtp. Is it necessary to have a complete smtp server on the local machine? Or is there a special smtp configuration? Greetings, Matthias

7 years, 2 months

2
3
0 0

Why make the decision to limit job context in lava master?

by Larry Shen

For 2019.04 version, we see next: Job context ----------- The schema validator is now checking the content of the `context` dictionary. Only the following keys are now allowed: * `arch`, `boot_console`, `boot_root`, `cpu`, `extra_options`, `guestfs_driveid`, `guestfs_interface`, `guestfs_size`, `machine`, `memory`, `model`, `monitor`, `netdevice`, `serial`, `vga` * `bootloader_prompt`, `console_device`, `extra_kernel_args`, `extra_nfsroot_args`, `kernel_loglevel`, `kernel_start_message`, `lava_test_results_dir`, `menu_interrupt_prompt`, `mustang_menu_list`, `test_character_delay`, `tftp_mac_address` Jobs using keys that are not listed in this list will be rejected. We usually set an customized context in job, and in device-type jinja2, use this context to just different value to set proper parameters. After this limit, all things break! So, my question is: lava could be designed to as a framework to give freedom to users to do their things as in the past, why we now enhance so many limits to users? And additional, and workaround for my scenario? Regards, Larry

7 years, 2 months

2
1
0 0

Board use rate in Lava?

by Denis HUMEAU

Dear users, I'd like to add metrics to scale my test farm. Basically I would like to check the occupation rate of the active boards in my farm, to be able to decide whether I need to add extra ones or not. Do you know if there is a simple way to do it? Best regards, Denis

7 years, 2 months

2
1
0 0

lxc test error

by jack lu

Hi, In my lava environment (debian 9.5 stretch, lava version:2019.04+stretch).When run a simple lxc test job.It happend a error: <http://192.168.101.205/scheduler/job/8#L83>Lxc container rootfs not found .. <http://192.168.101.205/scheduler/job/8#L101>LAVABug: This is probably a bug in LAVA, please report it. job definition is a simple lxc job from lava document: device_type: lxcjob_name: lxc-fedoratimeouts: job: minutes: 30 action: minutes: 5priority: mediumvisibility: public metadata: source: https://git.linaro.org/lava-team/refactoring.git path: lxc-fedora.yaml protocols: lava-lxc: name: pipeline-lxc-test distribution: fedora release: '26' arch: amd64 actions:- deploy: timeout: minutes: 30 to: lxc - boot: prompts: - '[root(a)(.*) /]#' timeout: minutes: 5 method: lxc - test: timeout: minutes: 5 definitions: - repository: http://git.linaro.org/lava-team/lava-functional-tests.git from: git path: lava-test-shell/smoke-tests-basic.yaml name: smoke-tests

7 years, 2 months

1
0
0 0

about multinode api parameter file overwritten

by jack lu

The multinode function of "pass data between devices".Note: "The message data is stored in a cache file which will be overwritten when the next synchronisation call is made. Ensure that your scripts make use of (or copy aside) any MultiNode cache data before calling any other MultiNode API helpers that may clear the cache." Does it mean follow example: roler1: .. steps: - lava-send ipv4 ip=192 - lava-send ipv4 ip=193 .. roler2: step2: - lava-wait ipv4 - ipdata=$(cat /tmp/lava_multi_node_cache.txt | cut -d = -f 2) .. After run, is content of roler2 ipdata 193?

7 years, 2 months

2
6
0 0

How to handle udev events when lava dispatcher is in a container

by Kumar Gala

In trying to run lava-dispatcher inside a docker container and connect a FRDM-K64F board ran into some issues related to the fact that udev events aren’t seen inside the container since we aren’t typically running systemd/udevd there. I came across this project that will forward udev events from the host to a container that worked pretty well: https://github.com/eiz/udevfw I’ve re-implemented this in python for easier development (added some docker awareness): https://git.lavasoftware.org/galak/docker-compose/blob/lite/contrib/udev-fo… Right now running udev-forward.py is kinda kludgy. Wanted to get input on how people think this should work, should we make a daemon out of it? Should there be some kinda of config file? Do we think we need to filter events (and if so how)? Need to look at support for multicasting (support sending to multiple dispatchers). Where should this live, in docker-compose repo? Other thoughts. - k

7 years, 2 months

1
1
0 0

lavacli device-type template set: Permission denied

by Kevin Hilman

Hello, I have a remote worker that needs to add a new device-type on the master. The remote worker has an auth token with admin/staff/superuser privileges, and lavacli configured with that token, but when I attempt to set the new template, I get permission denied: # lavacli device-types template set da850-lcdk /tmp/new-device-type.jinja2 Unable to call 'device-types.template': <Fault 400: 'Unable to write device-type configuration: Permission denied'> What permissions am I missing? Kevin

7 years, 2 months

2
1
0 0

Re: [Lava-users] [EXT] can LAVA support Python?

by White Weng

We have an internal automation framework supports Python, and would like to migrate to LAVA. can LAVA support Python? Thanks White Weng

7 years, 2 months

2
1
0 0

Issue with 2019.04 containers and static/docs/v2/

by Dan Rue

Hi! I'm seeing the following issue with lavasoftware/lava-server:2019.04: http://localhost/static/docs/v2/ gives "Forbidden". Apache log shows the following: [Mon May 06 17:57:42.206713 2019] [autoindex:error] [pid 766:tid 140404225701632] [client 172.18.0.1:46780] AH01276: Cannot serve directory /usr/share/lava-server/static/docs/v2/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm) found, and server-generated directory index forbidden by Options directive, referer: http://localhost/ The easiest way to reproduce is to run: $ docker run --rm -p 80:80 -it lavasoftware/lava-server:2019.04 And load http://localhost/static/docs/v2/ Change 2019.04 to 2019.03 and it works fine. I didn't see anything about this mentioned in the release announcement. I guess the apache config needs some update? Thanks! Dan

7 years, 2 months

2
5
0 0

[PATCH] doc/v2/timeouts: fix http-download action name typos

by Kevin Hilman

The name of the action for http download uses a hyphen, not an underscore. Fix the typos. Signed-off-by: Kevin Hilman <khilman(a)baylibre.com> --- doc/v2/timeouts.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/v2/timeouts.rst b/doc/v2/timeouts.rst index c330f9d89548..50070766abe0 100644 --- a/doc/v2/timeouts.rst +++ b/doc/v2/timeouts.rst @@ -259,7 +259,7 @@ block override. timeouts: actions: - http_download: + http-download: minutes: 2 .. _individual_connection_timeout_overrides: @@ -275,7 +275,7 @@ specific connection timeout which can be longer or shorter than the default. timeouts: connections: - http_download: + http-download: minutes: 2 .. _action_block_timeout_overrides: -- 2.21.0

7 years, 2 months

2
4
0 0

Current LAVA version in stretch-backports

by Tim Jaacks

Hello everyone, the current LAVA version in stretch-backports is still 2018-11. Is there a reason why it has not been updated since then? Will newer releases go into buster only? Or will there be updates in stretch-backports in the future? For stretch users, do you recommend using the LAVA repositories to upgrade to the latest version? Or should production systems keep using 2018-11 at this moment? Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Tempowerkring 2 21079 Hamburg Direct: +49 40 791 899 - 55 Fax: +49 40 791899 - 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com<http://www.garz-fricke.com/> WE MAKE IT YOURS! [cid:image001.jpg@01D4FF4A.A2ED9910] Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun

7 years, 3 months

2
1
0 0

Re: [Lava-users] Handling of a kernel panic

by Remi Duraffort

Hello, as said in the previous email, that's currently not possible to see kernel crashes outside of the boot action. That's something we want to improve. I will soon create an issue in our gitlab instance where you would be able to comment. Rgds Le jeu. 11 avr. 2019 à 14:33, Frank, Matthias <Matthias.Frank(a)tq-group.com> > a écrit : > > Hi lava users, > > > > sometimes I how in memory allocator stress tests a kernel panic. How can I > evaluate this? Is it possible to set a testcase or job to fail if a kernel > panic occurs? > > > > Matthias > > > > Sometimes a test triggers a kernel panic and the dut will reboot to U-Boot > and stuck because there is no boot process. Lava waits until timeout and > stop the job. > > > -- Rémi Duraffort LAVA Team, Linaro

7 years, 3 months

1
0
0 0

What's the difference between kernel ci's docker and official docker?

by Larry Shen

Hi, I'd like to know is this site official? https://github.com/kernelci/lava-docker Does this project same as the one in dockerhub, lavasoftware/lava-server?

7 years, 3 months

3
2
0 0

Correct way to make device not affect others.

by cnspring2002

I attach a tag on one of my device, and when submit job I will add "tags:" to my job, it's ok. But, when others submit their job with same device-type which same as my device, as they did not specify "tags", they will have chance to run their job on my device. How to avoid it? I want the job not be scheduled to the device which have a tag if the job did not specify any tag. I tried to set the device as private, but then only me can use this device, I have other guys in groupA which want to use the device, while I hae another some guys in groupB which didid not want to use these devices as some modules on the device is not same.

7 years, 3 months

3
2
0 0

device type alias redesign

by Milosz Wasilewski

Hi, There is an idea of device type 'alias' in LAVA. I don't quite understand what the use case for the current implementation was [1]. I tried using it but it wasn't very useful. My use case is that I need to submit jobs to a device type with different device type name. This is used to align device type naming between different labs in a bigger project (kernelci.org in this case). So the questions I have about current implementation: - is there anyone using current implementation? - if current implementation is used, how much trouble would it cause to change the behaviour? Change in behaviour is quite intrusive and will require database migration. [1] https://master.lavasoftware.org/static/docs/v2/glossary.html#term-alias Regards, milosz

7 years, 3 months

4
4
0 0

Handling of a kernel panic

by Frank, Matthias

Hi lava users, sometimes I how in memory allocator stress tests a kernel panic. How can I evaluate this? Is it possible to set a testcase or job to fail if a kernel panic occurs? Matthias

7 years, 3 months

2
1
0 0

[PATCH] Set systemd test data directory

by Khouloud Touil

In case that 'systemd' is one of the ptest to run and to avoid some test cases failure in the systemd ptest, we need to export the proper directory that contains the needed systemd test data. This patch exports the needed test data directory. Signed-off-by: Khouloud Touil <ktouil(a)baylibre.com> --- automated/linux/ptest/ptest.yaml | 1 + automated/linux/ptest/set-systemd-test-data.sh | 18 ++++++++++++++++++ 2 files changed, 19 insertions(+) create mode 100755 automated/linux/ptest/set-systemd-test-data.sh diff --git a/automated/linux/ptest/ptest.yaml b/automated/linux/ptest/ptest.yaml index 6205c11..85f6893 100644 --- a/automated/linux/ptest/ptest.yaml +++ b/automated/linux/ptest/ptest.yaml @@ -21,5 +21,6 @@ params: run: steps: - cd ./automated/linux/ptest + - ./set-systemd-test-data.sh $TESTS - PYTHONIOENCODING=UTF-8 ./ptest.py -o ./result.txt -t ${TESTS} -e ${EXCLUDE} - ../../utils/send-to-lava.sh ./result.txt diff --git a/automated/linux/ptest/set-systemd-test-data.sh b/automated/linux/ptest/set-systemd-test-data.sh new file mode 100755 index 0000000..0a26b4b --- /dev/null +++ b/automated/linux/ptest/set-systemd-test-data.sh @@ -0,0 +1,18 @@ +#!/bin/bash +#------------------------ +# Some systemd tests needs systemd test data +# to pass. +# This script test when there is systemd tests +# and set the systemd test data +#------------------------ +tests="$*" +test_dirs=['/usr/lib/systemd/ptest/tests/test', '/usr/lib64/systemd/ptest/tests/test', '/usr/lib32/systemd/ptest/tests/test'] +for t in $tests; do + if [ "$t" == "systemd" ]; then + for dir in test_dirs ; do + if [ -e "$dir" ]; then + export SYSTEMD_TEST_DATA=$dir + fi + done + fi +done \ No newline at end of file -- 2.17.1

7 years, 3 months

2
1
0 0

lava-os-build

by Frank, Matthias

Hi lava users, I have tested lava-os-build on my ptxdist root images and I got this output: root@MBa6x:/lava-557/bin ./lava-os-build _____ ___ ____ _ |_ _/ _ \\ / ___| _ _ ___| |_ ___ _ __ ___root@MBa6x:/lava-557/bin Maybe it's better to look for other files first, like /etc/os-release (or /usr/lib/os-release) for systemd systems. This file is (more) standardized way to detect with os/build is running by evaluating the keys NAME,PRETTY_NAME etc. What is the exact function of lava-os-build? Only diagnostic purpose to find out with os is running? Does something else rely on lava-os-build? What could break if I change that script? Matthias [0] https://www.freedesktop.org/software/systemd/man/os-release.html

7 years, 3 months

2
1
0 0

lxc job error: Lxc container rootfs not found

by jack lu

Hi,according https://validation.linaro.org/static/docs/v2/deploy-lxc.html?highlight=lxc. I run a sample lxc Job Definition as above.. the error msg : Lxc container rootfs not found

7 years, 3 months

2
3
0 0

LAVA Ansible playbooks

by Karsten Tausche

Hi, Are the Ansible playbook for setting up LAVA available somewhere? There is an old migrated issue on GitLab [1] which is closed, but the link to an implementation in there is dead. Is that playbook only internally available for Linaro? Is there anything you could share? It looks like many people are moving to Docker in the moment, but that's not an option for us (at least not for dispatchers), as we need LXC for Android testing. Cheers, Karsten [1] https://git.lavasoftware.org/lava/lava/issues/27

7 years, 3 months

3
4
0 0

LAVA Django template caching

by Karsten Tausche

Hi all, The LAVA docs mention that it's possible to enable template caching via settings.conf [1]. However, doing so leads to a key error when starting the LAVA gunicorn server and in `lava-server manage check --deploy`: ... File "/usr/lib/python3/dist-packages/lava_server/settings/distro.py", line 185, in <module> ("django.template.loaders.cached.Loader", TEMPLATES[0]["OPTIONS"]["loaders"]) KeyError: 'loaders' The LAVA git history shows that this dictionary key was removed in commit 6705ec870[2], "Refresh the setting files". Is this just a bug in LAVA, is Django template caching not supported anymore with LAVA, or are other Debian/pip packages required to be installed to enable to cache? I'm currently testing that on Debian buster, which ships Django version 1.11. Cheers, Karsten [1] https://validation.linaro.org/static/docs/v2/advanced-installation.html?hig… [2] https://git.lavasoftware.org/lava/lava/commit/6705ec870c1f30ea0b7f78f05a322…

7 years, 3 months

2
1
0 0

simple multinode job

by Frank, Matthias

Hi lava users, I want to try the simple client/server multi node job [0]. My job yaml is below. I get following error during job submission via webui: Job submission error: 'dict_keys' object does not support indexing What is wrong? The error message (a python error?) gives me no hint. The log files had have no entries for that issue. Greetings, Matthias job_name: simple multinode timeouts: job: minutes: 90 action: minutes: 10 connection: minutes: 2 priority: medium visibility: public protocols: lava-multinode: roles: server: device_type: tqma6s-mba6x count: 1 client: device_type: tqma6d-mba6x count: 1 timeout: minutes: 6 actions: - deploy: role: - server timeout: minutes: 10 to: tftp kernel: url: <url linuximage> type: zimage nfsrootfs: url: <url rootfs> compression: gz dtb: url: <url dtb> - deploy: role: - client timeout: minutes: 10 to: tftp kernel: url: <url linuximage> type: zimage nfsrootfs: url: <url rootfs> compression: gz dtb: url: <url dtb> - boot: role: - server method: u-boot commands: nfs auto_login: login_prompt: 'MBa6x login:' username: root prompts: - 'root@MBa6x:~' - boot: role: - client method: u-boot commands: nfs auto_login: login_prompt: 'MBa6x login:' username: root prompts: - 'root@MBa6x:~' - test: timeout: minutes: 120 definitions: - repository: <url git> from: git path: simple_multinode.yaml name: simple_multinode [0] https://validation.linaro.org/static/docs/v2/multinodeapi.html#example-1-si…

7 years, 3 months

3
4
0 0

lava-server upgrade to 2019-03

by Frank, Matthias

Hi lava-users, I upgrade my lava-server package (from backports) to 2019-03 on debian stretch. After this is get an django error: ERROR 2019-04-04 08:24:16,694 exception Invalid HTTP_HOST header: '<my-host-name>'. You may need to add '<my-host-name>' to ALLOWED_HOSTS. The browser reports a Bad Request (400) So I added <my-host-name> and "*" to ALLOWED_HOSTS in /usr/lib/python3/dist-packages/lava_scheduler_app/settings.py and /usr/lib/python3/dist-packages/django/conf/global_settings.py but the error is still present. Are these the wrong file or what could be the problem? Matthias

7 years, 3 months

3
2
0 0

Lava Issue: API-Error-server.scheduler.all_devices

by Chenchun (coston)

Job definition & Detailed log in attachment 发件人: Xiaomingwang (Steve) 发送时间: 2019年4月4日 10:29 收件人: lava-users(a)lists.lavasoftware.org 抄送: Yewenzhong (jackyewenzhong) <jack.yewenzhong(a)huawei.com>; Chenchun (coston) <chenchun7(a)huawei.com>; liucaili (A) <liucaili2(a)huawei.com> 主题: 转发: Lava Issue: API-Error-server.scheduler.all_devices 发件人: liucaili (A) 发送时间: 2019年4月4日 10:24 收件人: Xiaomingwang (Steve) <xiaomingwang1(a)huawei.com<mailto:xiaomingwang1@huawei.com>> 主题: Lava Issue: API-Error-server.scheduler.all_devices Dear Sir/Madam, If possible could you please help us analyze the problems encountered in recent Lava tests? Job definition & Detailed log in the attachment. lava-dispatcher version: 2018.11+stretch. The key information is as follows: python /usr/local/bin/module_deploy.py --DUT cloudgame4_01 Traceback (most recent call last): File "/usr/local/bin/module_deploy.py", line 37, in <module> main(args) File "/usr/local/bin/module_deploy.py", line 30, in main module = get_module(dut) File "/usr/local/bin/module_deploy.py", line 14, in get_module devices_list = server.scheduler.all_devices() File "/usr/lib/python2.7/xmlrpclib.py", line 1243, in __call__ return self.__send(self.__name, args) File "/usr/lib/python2.7/xmlrpclib.py", line 1602, in __request verbose=self.__verbose File "/usr/lib/python2.7/xmlrpclib.py", line 1283, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib/python2.7/xmlrpclib.py", line 1316, in single_request return self.parse_response(response) File "/usr/lib/python2.7/xmlrpclib.py", line 1493, in parse_response return u.close() File "/usr/lib/python2.7/xmlrpclib.py", line 800, in close raise Fault(**self._stack[0]) xmlrpclib.Fault: <Fault -32603: "Internal Server Error (contact server administrator for details): 'NoneType' object has no attribute 'pk'"> Is it a lava bug? We look forward to your reply. Thank you for your assistance. Best Regards, Caili Liu

7 years, 3 months

2
1
0 0

Override method param per device?

by Kumar Gala

Guys, Is it possible for one board/device instance to override a methods param? Specifically if I want to set ‘resets_after_flash’ to ’true’ for one disco-l475-iot1 board instance. Here’s the device type definition: https://git.lavasoftware.org/lava/lava/blob/master/lava_scheduler_app/tests… thanks - k

7 years, 3 months

2
1
0 0

record measurement

by Frank, Matthias

Hi, I want to measure some output values of test cases. I have a shell script which run stress-ng, parse it's output and exports some measurement variables. How can I record theses variables? I tried to use lava-test-case -shell myscript.sh -result pass -measurement $VAR1 -unit unit but no values are recorded. Maybe this is the wrong approach, but how can I do this in the correct way? Matthias

7 years, 3 months

2
3
0 0

Using Fuego with LAVA MultiNode API

by Chase Qi

Hi, In case it is any help for other LAVA and Fuego users, here is another option to run Fuego tests with LAVA MultiNode API. https://github.com/Linaro/test-definitions/blob/master/automated/linux/fueg… Thanks, Chase

7 years, 3 months

1
0
0 0

Running MultiNode job on specific devices

by Frank, Matthias

Hello lava users, how can I run a multinode job on specific devices instead of (a possible set) of device_types? I plan to run CAN or RS485 communication tests which requires a wired connection between duts. Is is possible to submit a job to theses special duts or should is have device_types with only on device instance? Greetings, Matthias

7 years, 3 months

3
2
0 0

Deploying and maintaining a LAVA Lab

by Dave Pigott

Hi all, We’ve started a collaborate page on how to deploy and maintain devices and instances of LAVA Labs. https://collaborate.linaro.org/display/CTT/LAB+Device+Deployment+Guide <https://collaborate.linaro.org/display/CTT/LAB+Device+Deployment+Guide> Please understand that this is a work in progress. All suggestions for changes and additions are more than welcome. email lava-lab-team(a)linaro.org with questions and suggestions. Dave ---------------- Dave Pigott LAVA Lab Lead Linaro Ltd t: (+44) (0) 1223 400063

7 years, 3 months

2
2
0 0

What happened if different worker link to different coordinator in one lava instance?

by cnspring2002

As title: What happened if different worker link to different coordinator in one lava instance for multinode job?

7 years, 4 months

3
2
0 0

query about lava usage for MCU like solution

by Hake Huang

Hi Sirs, Does LAVA support MCU like system? Which usually using a debugger to download image to a MCU internal flash, and get uart result? Regards, Hake

7 years, 4 months

3
5
0 0

jobs using notify with tokens, resubmit as different user

by Kevin Hilman

How can you have more than one LAVA user have the same token secret (e.g. for a notify callback.)? Example use case: - LAVA job with notify callbacks using token names - submited as user "bob", token names of "bob" map to actual token secrets - job fails - user "lab-admin" fixes some lab issues, re-submits job - job passes, but callbacks fail because tokens are associated with user "bob" Since the re-submitted job runs as user "lab-admin", the same token names and corresponding secrets don't exist. Naively, user "lab-admin" tries to copy the token secrets from user "bob" keeping the same token names, but this fails saying that "secret already exists". Why can't different users have the same secrets? I haven't looked at the code, but this limitation kind of suggests that the secret itself is the key in the db, which would prevent multiple secrets of the same. Kevin

7 years, 4 months

3
5
0 0

kexec boot mechanism

by Hemanth K V

Hello Lava-users, Do we have any sample reference yaml job definition which has booting the target with kexec method. Thanks, Hemanth.

7 years, 4 months

4
7
0 0

Build information in metadata

by Frank, Matthias

Hello lava users, I use in a test job linuximage, rootfs and dtb from file server location retrieved via http. These files are nightly build from Jenkins. The file links are static so I can use new images within the same test job definition. Jenkins generates also a build information text file with commit IDs an so on. How can I integrate the content of this file in the job metadata or job result log? Using metadata: build-readme: <link> in the job definition is not possible because the link is stable over different build, but the file content is changing. The DUT has no access to the file location because it is in an isolated network. Is there a way to cat the file content on the worker to metadata or job result? Greetings, Matthias

7 years, 4 months

2
1
0 0

Invalid device configuration

by Frank, Matthias

Hello lava users, my lava 2019.01 shows me a device with Health == Bad. The Transitions log give that message: March11, 3:02p.m. lava-health Good → Bad (Invalid device configuration) Where can I found information about a misconfigured device? The log files did not provide (in my eyes) sufficient information. As Health checks I use the smoke-tests. Kinds Regards, Matthias

7 years, 4 months

2
5
0 0

apt get install hang

by cnspring2002

I use lxc-mocker in docker container, everything is ok. Just if the package did not install in advance, then next command will hang in web: lxc-create -t ubuntu -n test_lava -- --release xenial --mirror http://mirror.bytemark.co.uk/debian --packages systemd,systemd-sysv --arch amd64 I enter the container, see: root@df67cf292479:/# ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 0 17:20 pts/0 00:00:00 /usr/bin/python3 /usr/bin/lava-slave --level DEBUG --log-file - --master tcp://192.168.1.10:5556 --socket-a root 8 0 0 17:20 pts/1 00:00:00 /bin/bash root 13 1 0 17:20 pts/0 00:00:00 lava-run [job: 837] root 19 13 0 17:20 pts/0 00:00:00 /bin/bash /usr/bin/lxc-create -q -t ubuntu -n test_lava -- --release xenial --mirror http://mirror.bytemark.c root 261 19 1 17:20 pts/0 00:00:00 apt-get -q install -y systemd systemd-sysv root 473 8 0 17:21 pts/1 00:00:00 ps -ef Seems "apt-get install" hang, but if I pre-install the systemd,etc, then everything will ok, the lxc-create will not hang. The same for lxc-attach mocker etc, all will hang if do "apt-get install" & no pakcage preinstall. Please suggest, thanks.

7 years, 4 months

2
4
0 0

docker-compose with lava

by Dan Rue

I started playing with the official lava images today and wanted to share my work in progress, in case others are doing something similar or have feedback. My goal is to deploy a lava lab locally. My architecture is a single host (for now) that will host both the lava server and one dispatcher. Once it's all working, I'll start deploying a qemu worker followed by some actual boards (hopefully). So far, I have the following docker-compose.yml: version: '3' services: database: image: postgres:9.6 environment: POSTGRES_USER: lavaserver POSTGRES_PASSWORD: mysecretpassword PGDATA: /var/lib/postgresql/data/pgdata volumes: - ${PWD}/pgdata:/var/lib/postgresql/data/pgdata server: image: lavasoftware/amd64-lava-server:2018.11 ports: - 80:80 volumes: - ${PWD}/etc/lava-server/settings.conf:/etc/lava-server/settings.conf - ${PWD}/etc/lava-server/instance.conf:/etc/lava-server/instance.conf depends_on: - database dispatcher: image: lavasoftware/amd64-lava-dispatcher:2018.11 environment: - "DISPATCHER_HOSTNAME=--hostname=dispatcher.lava.therub.org" - "LOGGER_URL=tcp://server:5555" - "MASTER_URL=tcp://server:5556" With that file, settings.conf, and instance.conf in place, I run 'mkdir pgdata; docker-compose up' and the 3 containers come up and start talking to each other. The only thing exposed to the outside world is lava-server's port 80 at the host's IP, which gives the lava homepage as expected. The first time they come up, the database isn't up fast enough (it has to initialize the first time) and lava-server fails to connect. If you cancel and run again it will connect the second time. A few things to note here. First, it doesn't seem like a persistent DB volume is possible with the existing lava-server container, because the DB is initialized at container build time rather than run-time, so there's not really a way to mount in a volume for the data. Anyway, postgres already solves this. In fact, I found their container documentation and entrypoint interface to be well done, so it may be a nice model to follow: https://hub.docker.com/_/postgres/ The server mostly works as listed above. I copied settings.conf and instance.conf out of the original container and into ./etc/lava-server/ and modified as needed. The dispatcher then runs and points to the server. It's notable that docker-compose by default sets up a docker network, allowing references to "database", "server", "dispatcher" to resolve within the containers. Once up, I ran the following to create my superuser: docker-compose exec server lava-server manage users add --staff --superuser --email dan.rue(a)linaro.org --passwd foo drue Now, for things I've run into and surprises: - When I used a local database, I could log in. With the database in a separate container, I can't. Not sure why yet. - I have the dreaded CSRF problem, which is unlikely to be related to docker, but the two vars in settings.conf didn't seem to help. (I'm terminating https outside of the container context, and then proxying into the container over http) - I was surprised there were no :latest containers published - I was surprised the containers were renamed to include the architecture name was in the container name. My understanding is that's the 'old' way to do it. The better way is to transparently detect arch using manifests. Again, see postgres/ as an example. - my pgdata/ directory gets chown'd when I run postgres container. I see the container has some support for running under a different uid, which I might try. - If the entrypoint of server supported some variables like LAVA_DB_PASSWORD, LAVA_DB_SERVER, SESSION_COOKIE_SECURE, etc, I wouldn't need to mount in things like instance.conf, settings.conf. I pushed my config used here to https://github.com/danrue/lava.home.therub.org. Git clone and then run 'docker-compose up' should just work. Anyway, thanks for the official images! They're a great start and will hopefully really simplify deploying lava. My next step is to debug some of the issues I mentioned above, and then start looking at dispatcher config (hopefully it's just a local volume mount). Dan

7 years, 5 months

4
23
0 0

AOSP multiple node job

by Chase Qi

Hi, In most cases, we don't need multiple node job as we can control AOSP DUT from lxc via adb over USB. However, here is the use case. CTS/VTS tradefed-shell --shards option supports to split tests and run them on multiple devices in parallel. To leverage the feature in LAVA, we need multinode job, right? And in multinode job, master-node lxc needs access to DUTs from salve nodes via adb over tcpip, right? Karsten shared a job example here[1]. This probably is the most advanced usage of LAVA, and probably also not encouraged? To make it more clear, the connectivity should look like this. master.lxc <----adb over usb----> master.dut master.lxc <----adb over tcpip ---> slave1.dut master.lxc <----adb over tcpip ---> slave2.dut .... I see two options for adb over tcpip. Option #1: WiFi. adb over wifi can be enabled easily by issuing adb cmds from lxc. I am not using it for two reasons. * WiFi isn't reliable for long cts/vts test run. * In Cambridge lab, WiFi sub-network isn't accessible from lxc network. Because of security concerns, there is no plan to change that. Option #2: Wired Ethernet. On devices like hikey, we need to run 'pre-os-command' in boot action to power off OTG port so that USB Ethernet dongle works. Once OTG port is off, lxc has no access to the DUT, then test definition should be executed on DUT, right? I am also having the following problems to do this. * Without context overriding, overlay tarball will be applied to '/system' directory and test job reported "/system/bin/sh: /lava-247856/bin/lava-test-runner: not found"[2]. * With the following job context, LAVA still runs '/lava-24/bin/lava-test-runner /lava-24/0' and it hangs there. It is tested in my local LAVA instance, test job definition and test log attached. Maybe my understanding on the context overriding is wrong, I thought LAVA should execute '/system/lava-24/bin/lava-test-runner /system/lava-24/0' instead. Any suggestions would be appreciated. context: lava_test_sh_cmd: '/system/bin/sh' lava_test_results_dir: '/system/lava-%s' I checked on the DUT directly, '/system/lava-%s' exist, but I cannot really run lava-test-runner. The shebang line seems problematic. --- hacking --- hikey:/system/lava-24/bin # ./lava-test-runner /system/bin/sh: ./lava-test-runner: No such file or directory hikey:/system/lava-24/bin # cat lava-test-runner #!/bin/bash #!/bin/sh .... # /system/bin/sh lava-test-runner lava-test-runner[18]: .: /lava/../bin/lava-common-functions: No such file or directory --- ends --- I had a discussion with Milosz. He proposed the third option which probably will be the most reliable one, but it is not supported in LAVA yet. Here is the idea. Milosz, feel free to explain more. **Option #3**: Add support for accessing to multiple DUTs in single node job. * Physically, we need the DUTs connected via USB cable to the same dispatcher. * In single node job, LAVA needs to add the DUTs specified(somehow) or assigned randomly(lets say both device type and numbers defined) to the same lxc container. Test definitions can take over from here. Is this can be done in LAVA? Can I require the feature? Any suggestions on the possible implementations? Thanks, Chase [1] https://review.linaro.org/#/c/qa/test-definitions/+/29417/4/automated/andro… [2] https://staging.validation.linaro.org/scheduler/job/247856#L1888

7 years, 5 months

3
6
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users