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

Failed to start lava-master.service: Unit lava-master.service not found.

by Singamsetty Nagendra

Hi, I am trying to upgrade the lava server and remote workers in my lab from 2020.08 to 2020.10(latest). *I have used following steps to upgrade:* $ wget https://apt.lavasoftware.org/lavasoftware.key.asc $ sudo apt-key add lavasoftware.key.asc OK sudo apt update sudo apt upgrade lava I am getting the following Error while restarting the lava-master : *root@LavaServer:/# service lava-master start Failed to start lava-master.service: Unit lava-master.service not found.* Even the remote worker side also got the same error message: *lava@alif-blr-worker02/# service lava-slave start Failed to start lava-slave.service: Unit lava-slave.service not found.* Able to start/stop lava-server-gunicorn root@LavaServer:/# service lava-server-gunicorn start On Master(lava server): following services are enabled after upgrade(2020.10) *root@LavaServer:/# systemctl list-unit-files | grep enabled |grep lavalava-coordinator.service enabled lava-publisher.service enabled lava-scheduler.service enabled lava-server-gunicorn.service enabled lava-worker.service enabled root@LavaServer:/# root@LavaServer:/#* On Worker following services are enabled after upgrade:(2020.10) *lava@alif-blr-worker02:~$ systemctl list-unit-files | grep enabled |grep lavalava-worker.service enabled * Another Worker which is not upgraded to 2020.10 :(It is running with 2020.08) *Following services are Enabled * *root@alif-blr-worker03:/# systemctl list-unit-files | grep enabled |grep lavalava-coordinator.service enabled lava-logs.service enabled lava-master.service enabled lava-publisher.service enabled lava-server-gunicorn.service enabled lava-slave.service enabled root@alif-blr-worker03:/# * *I am getting this issue with 2020.10 . I haven't seen this issue with previous version upgrades. * Kindly help me out to solve this issue!! Thanks!! Regards Nagendra S

4 years, 2 months

2
1
0 0

Some question about lava V2 2018.11+stretch，waiting for your answer，thanks very much

by yangjianxiang

Hi lava： Some question about lava V2 2018.11+stretch： 1、 As lava running for weeks，it tasks minutes for the master to schedule jobs to the lava-slave ，and the normal time maybe 20s below. When we restar both lava master and lava slave，it schedule job in 20s again. Can you tell us how to solve the problem，thanks very mutch. [cid:image002.png@01D6F0D5.449B7F70] 2、we want to know how lava code works，can you give us some document. Sometimes we want to modify the lava steps，but we don’t know how to do.

4 years, 2 months

3
2
0 0

WG: Help with new device integration

by Marcel Trattner

Dear Lava-Team, I contacted you a few weeks ago for some help with the integration of a new device. We got a bit further thanks to you but we're faceing some new issues and we hoped that you could help us with this. We are using the official Docker-Compose<https://git.lavasoftware.org/lava/pkg/docker-compose> repository and specified a new device dictionary on the server container. As a device type we use a newly created device type that extends base-fastboot device-type, which looks like this: {% extends 'rse22.jinja2' %} {% set power_on_command = 'python ./root/power-control/ppson.py' %} {% set power_off_command = 'python ./root/power-control/ppsoff.py' %} {% soft_reboot_command = 'reboot' %} {% hard_reset_command = 'python ./root/power-control/ppsoff.py && sleep 5 && python ./root/power-control/ppson.py' %} {% set connection_list = [uart0] %} {% set connection_commands = {uart0: telnet <ip_host_machine> 7101} %} {% set connection_tags = {uart0: [primary, 'telnet']} %} But with this we received the following error: [cid:image001.png@01D6EE7C.31C35A90] The error disappeared however when we removed the following lines: {% set power_on_command = 'python ./root/power-control/ppson.py' %} {% set power_off_command = 'python ./root/power-control/ppsoff.py' %} {% soft_reboot_command = 'reboot' %} {% hard_reset_command = 'python ./root/power-control/ppsoff.py && sleep 5 && python ./root/power-control/ppson.py' %} With those lines we are trying to trigger the scripts, which control our power supply directly. Do we have to pay attention to the python dependencies in the scripts or could the error be in the definition itself? We thought, that we had at least configured the device dictionary sufficiently to have a connection to the device and start a very basic health check. Our device runs Linux, which is running Android on top. The Ser2Net connection has been configured according to the instructions on the repo as well (using the telnet command by itself worked fine). So we specified the health check like this: device_type: rsu job_name: Health Check for RSU timeouts: job: minutes: 30 action: minutes: 5 connection: minutes: 2 priority: medium visibility: public actions: - deploy: namespace: tlxc timeout: minutes: 5 to: lxc packages: - android-tools-adb - android-tools-fastboot - boot: method: lxc prompts: - 'root@(.*):/#' timeout: minutes: 5 - test: timeout: minutes: 4 definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: hello-world description: "say hello" os: - android scope: - functional run: steps: - apt -q update - pwd - echo "echo hello" # remember to use -y to allow apt to proceed without interaction # -q simplifies the apt output for logging. from: inline name: hello-world path: inline/hello-world.yaml When executing, we got the following error: [cid:image002.png@01D6EE7E.9CED3690] Could you please give us some advice, on how to define a test job/health check for a device, which uses fast-boot and Android? Your help would be greatly appreciated. Best regards, Marcel _________________________________________________________ EMAIL LEGAL MENTION / DISCLAIMER This message contains information that may be privileged or confidential and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. Ce message contient des informations qui peuvent ?tre privil?gi?es ou confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le Bretonneux-France. Il est destin? uniquement ? la personne ? qui est adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce message ou toute partie de celui-ci. Si vous recevez ce message par erreur, veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les copies de ce message.

4 years, 2 months

2
1
0 0

Define "Missing key" Whitelist

by Westermann, Oliver

Hey, we recently updated our LAVA setup from 2020.06 to 2020.12. After a few hickups we’re back running, but we are greeted with a few new warnings: Our setup uses the iMX8 and the UUU boot method, which uses several, internal variables. Internal = Internal to U-Boot or bash, for example: > FB: ucmd setenv fastboot_buffer ${loadaddr} > FBK: ucmd mkfs.ext4 -F -E nodiscard /dev/mmcblk${mfg_mmcdev}p1 With the recent LAVA version, this causes a warning: {"dt": "2021-01-25T07:43:46.551216", "lvl": "warning", "msg": "Missing key : '{mfg_mmcdev}' for string 'ucmd mkfs.ext4 -F -E nodiscard /dev/mmcblk${mfg_mmcdev}p1'"} While I could reduce this by removing the brackets in the first case, this won’t work for the second case. Is there a way to provide eg a variable whitelist? The 30 warnings boil down to 4-5 variables, so this might be a useful feature addition. Any other ideas of cause welcome, maybe I will try to use this for my first contribution here 😊 Best regards, Olli

4 years, 2 months

2
1
0 0

Docker transfer_overlays problem

by Seb Seb

Hi, I am having a problem with using the transfer_overlays command for a dispatcher in docker. I cannot set the dispatcher ip no matter what I try. I have tried using the API here : " http://10.1.51.55/api/v0.2/workers/docker_dispatcher_hostname/config/" but I get this error when posting : ""detail": "CSRF Failed: CSRF token missing or incorrect.", I have tried another browser already. I have also tried creating a dispatcher.yaml file in these locations : /etc/lava-server/dispatcher.d/lava-dispatcher ; /etc/lava-server/dispatcher.d/ ; /etc/lava-server/dispatcher.d/lava-master. The ip I have set is simply ignored. Could anybody help please? Thanks

4 years, 2 months

2
1
0 0

Some question about lava V2 2018.11+stretch，waiting for your answer，thanks very much

by yangjianxiang

Hi lava： Some question about lava V2 2018.11+stretch： 1、 As lava running for weeks，it tasks minutes for the master to schedule jobs to the lava-slave ，and the normal time maybe 20s below. When we restar both lava master and lava slave，it schedule job in 20s again. Can you tell us how to solve the problem，thanks very mutch. [cid:image001.png@01D6ED8C.7BAFA000] 2、we want to know how lava code works，can you give us some document. Sometimes we want to modify the lava steps，but we don’t know how to do.

4 years, 3 months

1
0
0 0

Ask android vts test link in docker test shell.

by Larry Shen

Hi, guys, Recently we are running android VTS test in lava docker test shell, but find all MTP cases fail. It reports: 01-08 07:42:38 D/ModuleDefinition: Running module armeabi-v7a HalUsbGadgetV1_0HostTest 01-08 07:42:43 I/ModuleListener: [1/5] com.android.tests.usbgadget.HalUsbGadgetV1_0HostTest#testMtp FAILURE: java.lang.AssertionError: MTP not present at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at com.android.tests.usbgadget.HalUsbGadgetV1_0HostTest.testMtp(HalUsbGadgetV1_0HostTest.java:113) I'm a little lost currently, so before I have a deep investigation, I want to know if you can share a link about this case: com.android.tests.usbgadget.HalUsbGadgetV1_0HostTest#testMtp I know you guys run android tests on other product always, could share a link for us to reference? Or with good luck you know what's the potential root cause for my failure? Thanks.

4 years, 3 months

1
3
0 0

Unable to find settings.conf file in /etc/lava-server/ using 2020.10

by Nagendra Singamsetti

Hi team, I am Re installing my lava machines with 2020.10. But after upgrading I have noticed that settings.conf file is missing /etc/lava-server . Is this expected behaviour?? 2. I am unable to access the lava server within the intranet with the latest version 2020.10. To do this I used to modify settings.conf at /etc/lava-server/settings.conf with "ALLOWED_HOSTS" to "*". But i am getting Bad Request (400) Kindly help me out to solve this issue!! thanks Regards Nagendra S

4 years, 4 months

2
1
0 0

LAVA apt install packages

by Philippe Mazet (OSS)

Hi, It looks like the apt release is stuck to version 2019.11: https://apt.lavasoftware.org/release/dists/buster/Release Do I miss something? Then I tried to use the daily apt source to install a worker (deb https://apt.lavasoftware.org/daily buster main, mentioned on https://docs.lavasoftware.org/lava/installing_on_debian.html#debian-install…), but then I have a version mismatch with my master... Sorry to insist... but this version check is really a pain for us. A warning instead would be much more convenient. Could you please let me know how could I force install of 2020.10 for example? (I mean, a native install, not using Docker) Thank you very much, Philippe

4 years, 4 months

2
2
0 0

Re: [Lava-users] How can I upgrade my Lava software to latest version (may be 2020.10)

by koti koti

Hi Stevan, I have followed the steps mentioned in the pages provided by you i.e " https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-repositor… " Still my version is same i.e "2019.01-5" You can find my complete log at https://justpaste.me/id5P . Only the thing is that I followed below steps 1. Install Debain buster 2. Run #sudo apt install lava 3. Run #sudo apt install lava-dispatcher 4. #wget https://apt.lavasoftware.org/lavasoftware.key.asc 5. #sudo apt-key add lavasoftware.key.asc 6. #sudo apt update appreciated any suggestions. Regards, Koti > > ------------------------------ > > Message: 3 > Date: Fri, 27 Nov 2020 08:57:14 +0100 > From: Stevan Radakovi? <stevan.radakovic(a)linaro.org> > To: lava-users(a)lists.lavasoftware.org > Subject: Re: [Lava-users] How can I upgrade my Lava software to latest > version (may be 2020.10) > Message-ID: <6c0c9fb0-069b-142c-59d1-2ff229f37031(a)linaro.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hello, > > There's everything regarding releases documented here: > > https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-repositor… > < > https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-repositor… > > > You will need to add LAVA signing key prior as described here: > > https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-archive-s… > < > https://docs.lavasoftware.org/lava/installing_on_debian.html#lava-archive-s… > > > > Cheers, > > > On 11/27/20 8:31 AM, koti koti wrote: > > Hi, > > > > Recently I have installed Lava-Master and Lava-Dispatcher using the > > steps mentioned below in the corresponding servers. > > > > ??????????????? Server: > > ???????????????? ###### > > ?????????????????????? ?? 1. #sudo install lava > > ???????????????? Worker (Dispatcher) > > ???????????????? ################### > > ????????????????????????? 1. #sudo install lava-dispatcher > > > > But the installeve Lava software version is the old version > (*2019.01-5*). > > > > Now I want to upgrade to latest (*may be 2020.10*) lava > > (https://git.lavasoftware.org/lava/lava/-/tags > > <https://git.lavasoftware.org/lava/lava/-/tags>) > > > > Please can someone let me know the steps to upgrade my lava version to > > the latest? > > > > > > Regards, > > Koti > > > > _______________________________________________ > > Lava-users mailing list > > Lava-users(a)lists.lavasoftware.org > > https://lists.lavasoftware.org/mailman/listinfo/lava-users > > -- > Stevan Radakovi? | LAVA Engineer > Linaro.org <www.linaro.org> ? Open source software for ARM SoCs > >

4 years, 4 months

2
5
0 0

Re: [Lava-users] Unable to upgrade lava server/workers 2020.10

by koti koti

Hi, Try to list the available lava versions in your distro initially using the command "apt policy lava" and downgrade using "sudo apt install <package version>" . But, there may be cases in which you must resolve some dependencies to be able to downgrade the package through. Hope this may helps you i.e https://www.linuxuprising.com/2019/02/how-to-downgrade-packages-to-specific… *Note*: We have not tried this so far. AFAIK before executing these commands, make sure you take the backup of your lava modified/configuration files which you have changed for your production/running setup. Best of luck!!. Regards, Koti On Thu, 10 Dec 2020 at 17:30, <lava-users-request(a)lists.lavasoftware.org> wrote: > > Date: Thu, 10 Dec 2020 17:20:08 +0530 > From: Nagendra Singamsetti <nag.singam91(a)gmail.com> > To: lava-users(a)lists.lavasoftware.org > Subject: [Lava-users] Unable to upgrade lava server/workers 2020.10 > Message-ID: > < > CAFhg_WuWOCMedoDXECg+rcFdtzwPS2ei5m8Q+mpFKjhTgKqa9w(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi Team, > > 1. I am trying to upgrade lava machines with the latest version > 2020.10.previously it was running on 2020.08. > > After Upgrading with the latest 2020.10 i can see that All machines 2 > workers & 1 server went offline. Unable to start services of server/worker > due to > > *Failed to start lava-master.service: Unit lava-master.service not found.* > > *Failed to start lava-slave.service: Unit lava-slave.service not found.* > > *i have referred following page to upgrade:* > > https://lava.readthedocs.io/en/latest/admin/basic-tutorials/instance/instal… > > > 2 . I would like to know how to downgrade to previous versions. > > I am looking for your kind response !! > > Regards > Nagendra S > > ***************************************** >

4 years, 4 months

1
0
0 0

Unable to upgrade lava server/workers 2020.10

by Nagendra Singamsetti

Hi Team, 1. I am trying to upgrade lava machines with the latest version 2020.10.previously it was running on 2020.08. After Upgrading with the latest 2020.10 i can see that All machines 2 workers & 1 server went offline. Unable to start services of server/worker due to *Failed to start lava-master.service: Unit lava-master.service not found.* *Failed to start lava-slave.service: Unit lava-slave.service not found.* *i have referred following page to upgrade:* https://lava.readthedocs.io/en/latest/admin/basic-tutorials/instance/instal… 2 . I would like to know how to downgrade to previous versions. I am looking for your kind response !! Regards Nagendra S

4 years, 4 months

1
0
0 0

Re: [Lava-users] [Lava-devel] Integration of a new device

by koti koti

++ Lava-users list. Regards, Koti On Fri, 4 Dec 2020 at 17:30, <lava-devel-request(a)lists.lavasoftware.org> wrote: > Send Lava-devel mailing list submissions to > lava-devel(a)lists.lavasoftware.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.lavasoftware.org/mailman/listinfo/lava-devel > or, via email, send a message with subject or body 'help' to > lava-devel-request(a)lists.lavasoftware.org > > You can reach the person managing the list at > lava-devel-owner(a)lists.lavasoftware.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Lava-devel digest..." > > > Today's Topics: > > 1. Integration of a new device (Marcel Trattner) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 4 Dec 2020 10:50:08 +0000 > From: Marcel Trattner <marcel.trattner(a)expleogroup.com> > To: "Lava-devel(a)lists.lavasoftware.org" > <Lava-devel(a)lists.lavasoftware.org> > Cc: Alexander Wyron Wachtberger > <alexander-wyron.wachtberger(a)expleogroup.com>, Vladimir Schmidt > <vladimir.schmidt(a)expleogroup.com> > Subject: [Lava-devel] Integration of a new device > Message-ID: > < > AM9PR10MB4295B7516795BD7B514C2DF7E5F10(a)AM9PR10MB4295.EURPRD10.PROD.OUTLOOK.COM > > > > Content-Type: text/plain; charset="us-ascii" > > Dear LAVA-Team, > > We have only recently started to use LAVA in a new project and we are now > at the point of integrating a new device. As I have read in the > documentation that this is the hardest part I would like to ask for some > advice where to start and what to especially look out for. > > The current state is that LAVA, as a master and one slave is running in > two Docker containers by using the example of the following Github > repository: > > https://github.com/kernelci/lava-docker > > After reading the documentary extensively and trying things out with qemu > I'd like to try and integrate the following device: > > https://www.lantronix.com/products/sa8155p-automotive-development-platform/ > > Our plan so far would be: > Since it has a Snapdragon processor, it's running Android and it is using > fastboot for flashing, we figured we could use one of the dragonboard > Device-Type templates and duplicate it for our device. But as it comes now > to configuring the device dictionary and specifying the test jobs we are > not so sure as how to proceed and we also don't want to damage the > hardware, so we would be grateful for some help. > > Here some more information: > The DUT is connected via USB and its power supply can be turned on and off > by using Python scripts (When defining the power_on and power_off commands, > should the scripts then be on the master or on the dispatcher? And what are > all the necessary parameters for the power on/off and also the values > connection_list and connection_commands?). > It is running Android with the underlying Linux configured especially for > the hardware, so we would like to avoid deploying for the beginning and > only run some simple shell tests to see if the connection stands. > A very simple health check has been set up here< > https://paste.debian.net/1175549>, maybe you could give some feedback if > that would be sufficient and how future test jobs should be altered. > > Hope to hear from you soon > > Best Regards, > > > _________________________________________________________ > > EMAIL LEGAL MENTION / DISCLAIMER > > This message contains information that may be privileged or confidential > and is the property of the Expleo Services SAS, RCS Versailles 831 178 348, > located, 3 avenue des Pr?s, 78180 Montigny Le Bretonneux - France. It is > intended only for the person to whom it is addressed. If you are not the > intended recipient, you are not authorized to read, print, retain, copy, > disseminate, distribute, or use this message or any part thereof. If you > receive this message in error, please notify the sender immediately and > delete all copies of this message. > > Ce message contient des informations qui peuvent ?tre privil?gi?es ou > confidentielles et elles sont de la propri?t? d'Expleo Services SAS, RCS > Versailles 831 178 348, situ?, 3 avenue des Pr?s, 78180 Montigny le > Bretonneux-France. Il est destin? uniquement ? la personne ? qui est > adress?. Si vous n'?tes pas le destinataire vis?, vous n'?tes pas autoris? > ? lire, imprimer, conserver, copier, diffuser, distribuer ou utiliser ce > message ou toute partie de celui-ci. Si vous recevez ce message par erreur, > veuillez en avertir imm?diatement l'exp?diteur et supprimer toutes les > copies de ce message. >

4 years, 4 months

1
0
0 0

Failed to start lava-master.service: Unit lava-master.service not found

by Nagendra Singamsetti

Hi, I am trying to upgrade the lava server and remote workers in my lab from 2020.08 to 2020.10(latest). *I have used following steps to upgrade:* $ wget https://apt.lavasoftware.org/lavasoftware.key.asc $ sudo apt-key add lavasoftware.key.asc OK sudo apt update sudo apt upgrade lava I am getting the following Error while restarting the lava-master : *root@LavaServer:/# service lava-master startFailed to start lava-master.service: Unit lava-master.service not found.* Even the remote worker side also got the same error message: *lava@alif-blr-worker02/# service lava-slave startFailed to start lava-slave.service: Unit lava-slave.service not found.* Able to start/stop lava-server-gunicorn root@LavaServer:/# service lava-server-gunicorn start On Master(lava server): following services are enabled after upgrade(2020.10) *root@LavaServer:/# systemctl list-unit-files | grep enabled |grep lavalava-coordinator.service enabled lava-publisher.service enabled lava-scheduler.service enabled lava-server-gunicorn.service enabled lava-worker.service enabled root@LavaServer:/#root@LavaServer:/#* On Worker following services are enabled after upgrade:(2020.10) *lava@alif-blr-worker02:~$ systemctl list-unit-files | grep enabled |grep lavalava-worker.service enabled * Another Worker which is not upgraded to 2020.10 :(It is running with 2020.08) *Following services are Enabled * *root@alif-blr-worker03:/# systemctl list-unit-files | grep enabled |grep lavalava-coordinator.service enabled lava-logs.service enabled lava-master.service enabled lava-publisher.service enabled lava-server-gunicorn.service enabled lava-slave.service enabled root@alif-blr-worker03:/# * *I am getting this issue with 2020.10 . I haven't seen this issue with previous version upgrades. * Kindly help me out to solve this issue!! Thanks!! Regards Nagendra S

4 years, 4 months

1
0
0 0

"lava-master.log" time stamp does not match to my LAVA "Debian" server time

by koti koti

Hi, It looks like my "lava-master.log ("/var/log/lava-server/lava-master.log)"" (even other lava logs) timestamp does not match to the lava installed server (Debain 10/Buster) time stamp. Do I need to run any command to make sure "lava server logs" timestamp sync with Lava server time stamp? output: ##################### Debian Time: ########### lavamaster@lavamaster:/var/log/lava-server$ date Tue Dec 1 17:37:59 IST 2020 lavamaster@lavamaster:/var/log/lava-server$ lava-master.log: ############# lavamaster@lavamaster:/var/log/lava-server$ tail -f lava-master.log 2020-12-01 12:02:51,507 DEBUG - qemu 2020-12-01 12:02:51,531 DEBUG lava-logs => PING(20) 2020-12-01 12:02:54,519 DEBUG lavamaster => PING(20) 2020-12-01 12:02:58,749 DEBUG raspberrypi => PING(20) 2020-12-01 12:03:11,534 INFO scheduling health checks: 2020-12-01 12:03:11,554 INFO scheduling jobs: 2020-12-01 12:03:11,556 DEBUG - qemu 2020-12-01 12:03:11,582 DEBUG lava-logs => PING(20) 2020-12-01 12:03:14,542 DEBUG lavamaster => PING(20) 2020-12-01 12:03:18,774 DEBUG raspberrypi => PING(20) 2020-12-01 12:03:31,582 INFO scheduling health checks: 2020-12-01 12:03:31,603 INFO scheduling jobs: 2020-12-01 12:03:31,605 DEBUG - qemu 2020-12-01 12:03:31,633 DEBUG lava-logs => PING(20) 2020-12-01 12:03:34,566 DEBUG lavamaster => PING(20) Regards, Koti

4 years, 4 months

2
2
0 0

How can I upgrade my Lava software to latest version (may be 2020.10)

by koti koti

Hi, Recently I have installed Lava-Master and Lava-Dispatcher using the steps mentioned below in the corresponding servers. Server: ###### 1. #sudo install lava Worker (Dispatcher) ################### 1. #sudo install lava-dispatcher But the installeve Lava software version is the old version (*2019.01-5*). Now I want to upgrade to latest (*may be 2020.10*) lava ( https://git.lavasoftware.org/lava/lava/-/tags) Please can someone let me know the steps to upgrade my lava version to the latest? Regards, Koti

4 years, 4 months

2
1
0 0

QEMU "Health-check" job still in running state on my first Remote Worker

by koti koti

Hi, Recently I have installed "LAVA-Master" on Server and "LAVA-Worker (On Remote location)" on Raspberrypi-4 (8GB). Installation steps: ############################### ############################### Server: ###### 1. #sudo install lava Worker (Raspberrypi-4) ################### 1. #sudo install lava-dispatcher Add worker to Master ############################### ############################### 1. sudo lava-server manage device-types add qemu 2. sudo lava-server manage devices add --device-type qemu --worker raspberrypi qemu-02 3. Now I am able to see "raspberrypi" worker in green colour state in the master under "LAVA--->Scheduler-->workers". Problem/issue: ############ 1. My QEMU job(Health-check) is still in running state even after 2 days (Attached the screenshot) even though it is working if my dispatcher is from the same master server. I feels something I missed here and may be extra setups to establish proper communication between "Master" and "Remote-Worker" Please can someone suggest me as what am I missing to complete my QEMU job(Health-check) while it running in "Remote-Worker" ? Regards, Koti

4 years, 4 months

1
1
0 0

Can't find serial port when test.

by cnspring2002

Dear all, I have one issue when use one qualcomn's development board: - test: definitions: - from: inline name: auto_test path: inline/auto_test.yaml repository: metadata: description: run format: Lava-Test name: run run: steps: - lava-test-case "Android_Serial_Case" --shell "./test.py" docker: image: myimage local: true timeout: minutes: 1600 The test.py is from our customer, when run it, it show the error: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/serial/serialposix.py", line 265, in open self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK) FileNotFoundError: [Errno 2] No such file or directory: '/dev/ttyUSB0' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/local/lib/python3.7/site-packages/serial/serialutil.py", line 240, in __init__ self.open() File "/usr/local/lib/python3.7/site-packages/serial/serialposix.py", line 268, in open raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg)) serial.serialutil.SerialException: [Errno 2] could not open port /dev/ttyUSB0: [Errno 2] No such file or directory: '/dev/ttyUSB0' I have linked the board to pc, and can see the "/dev/ttyUSB0" in my pc, what happened here?

4 years, 5 months

2
3
0 0

What's the suggestion for application which may need fuse in docker test shell?

by Larry Shen

Hi, We have a test which may need /dev/fuse when run in docker test shell, something like next: docker run -it --cap-add SYS_ADMIN --device /dev/fuse --security-opt apparmor:unconfined hello What's the suggestion for this case? Thanks.

4 years, 5 months

1
0
0 0

Moving boot commands from definition to device for UUU boot action

by Westermann, Oliver

Hey, I would like some advice on properly cleaning up my lava jobs. Following some examples, I now have job definitions that work for me. Each job definition contains a path to all images and the full list of boot commands, which are specific to our image setup and therefore ~40 lines, examples below. I would like to separate the boot commands into the device definition as those should stay stable and we only want to test the image files in the job. I've tried to move the -boot section to both the device definitions or the device type definition, but I did not manage to get a working boot out of that setup. If you would like to know what exactly I tried or need additional debug info, let me know. I've added @larry.shen@nxp.com as to my understanding he implemented the UUU actions, so maybe he has some good advice on best practices? Looking forward for some feedback and of cause thanks for the awesome piece of software to the developers! Best regards, Olli Example: actions: - deploy: to: uuu images: boot: url: file:///network-share/imx-boot.uuu initrd: url: file:///network-share/fitImage-fsl-image-mfgtool.bin [4 more image files] - boot: method: uuu commands: # Load SPL and U-Boot - SDP: boot -f {boot} - SDPU: delay 1000 - SDPU: write -f {boot} -offset 0x57c00 - SDPU: jump # run mfgtool ramdisk - FB: ucmd setenv fastboot_buffer ${loadaddr} - FB: download -f {initrd} [ 30 more commands ]

4 years, 5 months

2
3
0 0

Re: [Lava-users] lava-docker-worker: docker OCI runtime error

by K R, ANANTHA

Hi, I had installed docker long back and therefore not remember how I installed it exactly but I think I used "apt-get install docker.io" Here is the docker version running on my system. anantha@anantha-buster:~$ docker version Client: Version: 18.09.1 API version: 1.39 Go version: go1.11.6 Git commit: 4c52b90 Built: Sun, 14 Jun 2020 22:12:29 +0200 OS/Arch: linux/amd64 Experimental: false Server: Engine: Version: 18.09.1 API version: 1.39 (minimum version 1.12) Go version: go1.11.6 Git commit: 4c52b90 Built: Sun Jun 14 20:12:29 2020 OS/Arch: linux/amd64 Experimental: false Full log: https://paste.debian.net/1170559/ Will try with a fresh docker installation as in https://staging.validation.linaro.org/static/docs/v2/docker-admin.html#prer… From: K R, ANANTHA Sent: 06 November 2020 18:08 To: 'lava-users(a)lists.lavasoftware.org' <lava-users(a)lists.lavasoftware.org> Subject: RE: lava-docker-worker: docker OCI runtime error Hi all, I removed the "-init" flag passed to docker command in the /usr/lib/python3/dist-packages/docker_worker.py. After this the worker container started and is shown to be online in lava server web interface. Is this work around ok to be used ? I'm using the lava-docker-worker on a Debian buster (10.6) machine. Thank you, Anantha From: K R, ANANTHA Sent: 04 November 2020 20:37 To: 'lava-users(a)lists.lavasoftware.org' <lava-users(a)lists.lavasoftware.org<mailto:lava-users@lists.lavasoftware.org>> Subject: lava-docker-worker: docker OCI runtime error Hi All, This is my first post in lava support community. I was trying to setup worker using lava-docker-worker. Followed steps as documented here https://git.lavasoftware.org/lava/lava/-/blob/2020.09/doc/content/admin/adv… However I'm stuck with the error from docker daemon as shown in the bellow log. anantha@anantha-buster:~$ sudo lava-docker-worker -l DEBUG --url http://<My-LAVA-server-IP<http://%3cMy-LAVA-server-IP>> 2020.10: Pulling from lavasoftware/lava-dispatcher bb79b6b2107f: Pull complete 81b92962f1c3: Pull complete e69bdb4eac16: Pull complete Digest: sha256:27b3c2a84684bb0705e300899084bcbfcad99bc1fc1fd7917d8bec5ee47d57cb Status: Downloaded newer image for lavasoftware/lava-dispatcher:2020.10 docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. ^c Need help in regard to solve the above error. Thank you, Anantha

4 years, 5 months

1
0
0 0

Re: [Lava-users] lava-docker-worker: docker OCI runtime error

by K R, ANANTHA

Hi all, I removed the "-init" flag passed to docker command in the /usr/lib/python3/dist-packages/docker_worker.py. After this the worker container started and is shown to be online in lava server web interface. Is this work around ok to be used ? I'm using the lava-docker-worker on a Debian buster (10.6) machine. Thank you, Anantha From: K R, ANANTHA Sent: 04 November 2020 20:37 To: 'lava-users(a)lists.lavasoftware.org' <lava-users(a)lists.lavasoftware.org> Subject: lava-docker-worker: docker OCI runtime error Hi All, This is my first post in lava support community. I was trying to setup worker using lava-docker-worker. Followed steps as documented here https://git.lavasoftware.org/lava/lava/-/blob/2020.09/doc/content/admin/adv… However I'm stuck with the error from docker daemon as shown in the bellow log. anantha@anantha-buster:~$ sudo lava-docker-worker -l DEBUG --url http://<My-LAVA-server-IP<http://%3cMy-LAVA-server-IP>> 2020.10: Pulling from lavasoftware/lava-dispatcher bb79b6b2107f: Pull complete 81b92962f1c3: Pull complete e69bdb4eac16: Pull complete Digest: sha256:27b3c2a84684bb0705e300899084bcbfcad99bc1fc1fd7917d8bec5ee47d57cb Status: Downloaded newer image for lavasoftware/lava-dispatcher:2020.10 docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. ^c Need help in regard to solve the above error. Thank you, Anantha

4 years, 5 months

2
1
0 0

lava-docker-worker: docker OCI runtime error

by K R, ANANTHA

Hi All, This is my first post in lava support community. I was trying to setup worker using lava-docker-worker. Followed steps as documented here https://git.lavasoftware.org/lava/lava/-/blob/2020.09/doc/content/admin/adv… However I'm stuck with the error from docker daemon as shown in the bellow log. anantha@anantha-buster:~$ sudo lava-docker-worker -l DEBUG --url http://<My-LAVA-server-IP> 2020.10: Pulling from lavasoftware/lava-dispatcher bb79b6b2107f: Pull complete 81b92962f1c3: Pull complete e69bdb4eac16: Pull complete Digest: sha256:27b3c2a84684bb0705e300899084bcbfcad99bc1fc1fd7917d8bec5ee47d57cb Status: Downloaded newer image for lavasoftware/lava-dispatcher:2020.10 docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. docker: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "exec: \"/dev/init\": stat /dev/init: no such file or directory": unknown. ^c Need help in regard to solve the above error. Thank you, Anantha

4 years, 5 months

1
0
0 0

Re: [Lava-users] lava-docker-worker: how to customize?

by Philippe Mazet (OSS)

Thanks Milosz. 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). -----Original Message----- 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. milosz > > Finally, I noticed that if I don't do a "service tftpd-hpa restart", TFTP does not work. Is it a known issue? > > Thanks, > > Philippe Mazet > > _______________________________________________ > 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=04%7C01% > 7Cphilippe.mazet%40nxp.com%7Cde6159fe8c1e43cfcc0008d87bf1f211%7C686ea1 > d3bc2b4c6fa92cd99c5c301635%7C0%7C1%7C637395626367151208%7CUnknown%7CTW > FpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6 > Mn0%3D%7C3000&sdata=gElRt2xv5DouqTeQUF6nPlP33MUKUs68ZT8LWmB67%2Fc% > 3D&reserved=0 _______________________________________________ Lava-users mailing list Lava-users(a)lists.lavasoftware.org https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lav…

4 years, 5 months

2
2
0 0

lava-docker-worker: how to customize?

by Philippe Mazet (OSS)

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? Finally, I noticed that if I don't do a "service tftpd-hpa restart", TFTP does not work. Is it a known issue? Thanks, Philippe Mazet

4 years, 5 months

2
1
0 0

Error while using uuu boot method

by DAS, BHARGAV

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). Regards, Bhargav

4 years, 6 months

2
9
0 0

Job IMCOMPLETE for unknown reason

by Kever Yang

Hi 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 |--> [140442] scheduling 2020-10-10 09:40:58,486 INFO [140442] START => lava-slave247 (rv1126-evb-01) 2020-10-10 09:40:58,517 INFO [140442] lava-slave247 => START_OK 2020-10-10 09:41:09,539 DEBUG lava-logs => PING(20) 2020-10-10 09:41:13,537 INFO [140442] lava-slave247 => END (lava-run crashed, mark job as INCOMPLETE) 2020-10-10 09:41:13,759 ERROR [140442] Unable to dump 'description.yaml' 2020-10-10 09:41:13,759 ERROR [140442] Compressed data ended before the end-of-stream marker was reached Traceback (most recent call last): File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", 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 was reached 2020-10-10 09:41:13,763 DEBUG lava-slave241 => PING(20) Thanks, - Kever

4 years, 6 months

2
1
0 0

LAVA: How to link Requirements/"Any web page" page URL's to LAVA test cases

by koti koti

Hi, 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? Regards, Koti

4 years, 6 months

2
2
0 0

Re: [Lava-users] LAVA: How to link Requirements/"Any web page" page URL's to LAVA test cases

by koti koti

Hi, 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) Example: ####### metadata: Testcase ID : TestCase_ID: xxxxx Requirement Path: Requirement_URL_Page : XXXXX Regards, Koti On Mon, 19 Oct 2020 at 15:05, koti koti via groups.io <kotisoftwaretest= gmail.com(a)groups.io> wrote: > Hi, > > 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? > > Regards, > Koti > > > -=-=-=-=-=-=-=-=-=-=-=- > 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 [ > kotisoftwaretest(a)gmail.com] > -=-=-=-=-=-=-=-=-=-=-=- > > >

4 years, 6 months

1
0
0 0

LAVA : relays and PDU's info for dragonboard-845 DUT in India

by koti koti

Hi, 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 mode" . 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) Note: 1. I have found a couple of Relays URL's ( https://www.robot-electronics.co.uk/products/relay-modules/ethernet-relay/e…) . * But these are not available in India.* Regards, Koti

4 years, 6 months

2
2
0 0

Issues about XMLRPC & lavacli.

by Larry Shen

Hi, guys, We find an issue related to job submit: 1) One team use "lavacli" to submit request, and sometimes it will report next: 07-Sep-2020 16:37:35 Unable to connect: HTTPConnectionPool(host='lava-master.sw.nxp.com', port=80): Read timed out. (read timeout=20.0) Looks this error happens at next, what do you think about this issue? try: # Create the Transport object parsed_uri = urlparse(uri) transport = RequestsTransport( parsed_uri.scheme, config.get("proxy"), config.get("timeout", 20.0), config.get("verify_ssl_cert", True), ) # allow_none is True because the server does support it proxy = xmlrpc.client.ServerProxy(uri, allow_none=True, transport=transport) version = proxy.system.version() except (OSError, xmlrpc.client.Error) as exc: print("Unable to connect: %s" % exc2str(exc)) return 1 2) Another team write their own python code using XMLRPC to submit job, did something like next, it reports next: ERROR in XMLRPC.py:submitJob:63 msg: Failed to submit job, reason: <ProtocolError for chuan.su:chuan.su@lava-master.sw.nxp.com/RPC2: 502 Bad Gateway>! try: job_id = self.connection.scheduler.submit_job(job) self.logger.debug("Successed to submit job , job_id: %d, platform; %s!",job_id,platform) return job_id except Exception as e: self.logger.error("Failed to submit job, reason: %s!",str(e)) return None We are currently using lava server version 2020.08, guys told me in the past days, we also encountered similar, but with very low probability. But recently it becomes very high probability. I'd like to know if possible this will related to your changes to gunicorn eventlet? Or other possible reasons? Thanks, Larry

4 years, 6 months

3
17
0 0

Usb bus circulated issue for android.

by Larry Shen

Hi, guys, We found a blocking issue for android test, the story is next: 1. job #1 with device #1 is running for about 12 hours, during its run, it will restart the boards many times, then the usb path will e.g. start from /dev/bus/usb/003/001 to /dev/bus/usb/002, then /dev/bus/usb/003...... finally /dev/bus/usb/127. You know, the max number here will be 127, so, if device reset again, the number will back to 001. Adb devices in container 1: $ adb devices List of devices attached 040c41d4d72d7393 device 2. job #2 with device #2 starts run during the job #1 still running, then E.g. it will mknod /dev/bus/usb/003/016 to another docker-test-shell container, also cgroup privilege added. But as the /dev/bus/usb/003/016 was once used by job #1, and this node won't be deleted from docker-test-shell container. So, we find high probability the device #2 was seen in job #1's docker-test-shell container (Checked with adb devices). Now, adb devices in container 2: $adb devices List of devices attached After above, adb devices in container 1: $ adb devices List of devices attached 040c41d4d72d7393 device 23305a0a5c85d936 device This becomes a big issue for our parallel android test. In fact, in the old LXC days, we also find similar issues, so we made a workaround in our local: https://github.com/atline/lava-docker-slave/blob/66f15d9da88912fc929fef5213… In this patch, we also monitor "remove", ENV{ID_SERIAL_SHORT}, that is "if a usb leaved, let it delete the node". But, I don't know for which reasons, in current version(2020.08), now I can just monitor "remove" in udev, can't match "remove + ENV{ID_SERIAL_SHORT}" correctly. So, to make our local android run could work in a short time, we did a patch as next: # diff __init__.py.bak __init__.py 157,158c157,158 < "mkdir -p %s && mknod %s c %d %d || true" < % (os.path.dirname(node), node, major, minor), --- > "mkdir -p %s && rm -f %s/* && mknod %s c %d %d || true" > % (os.path.dirname(node), os.path.dirname(node), node, major, minor), Now, no issue happens in our side, but it looks this is somewhat not universal? So, I'm here to ask the question, have you ever found this issue? And what's your thought on this?

4 years, 7 months

3
2
0 0

U-boot reset Interactive test nethod

by DAS, BHARGAV

Hi Lava users, I am facing some issues while using the interactive test method, for testing u-boot reset function. In v2019.11 this worked perfectly but currently while using v2020.07 and this features seems to be broken. Or am I missing something here. Here detailed description of the issue: We are testing the u-boot reset command below is the snippet of the job definition ... ... ... - name: mmcinfo command: mmcinfo successes: - message: "Erase Group Size:" failures: - message: "Unknown command " error: "Unknown command " - name: reset command: reset successes: - message: "Hit any key to stop autoboot" failures: - message: "Unknown command " error: "Unknown command " So in v2019.11 once the "Hit any key to stop autoboot" string was matched the target switched off (check screenshot "reset-snippet-v2019-11.PNG"). But this is not working in v2020.07, after the success message is matched the target is not switched off (check screenshot "reset-snippet-v2020-07.PNG"). Regards, Bhargav

4 years, 7 months

2
3
0 0

About customize query in job page.

by Larry Shen

Hi, all, I want to do a job search with owner, E.g. in https://validation.linaro.org/scheduler/alljobs 's search box, I input next: owner_query=qa-reports-bot But, it return nothing to me, all jobs filtered out. I wonder what's the correct input in this search box for "Custom query text"? Regards, Larry

4 years, 7 months

2
2
0 0

Adding new device issue

by Koturappa, Hemanth

Hello Lava-Users, When we try to add new device we are facing the error 500 Internal Server Error maximum recursion depth exceeded in comparison Oops, something has gone wrong! Recently we had updated the LAVA instance server to Debian10. The LAVA server version presently running on the instance is lava_admin@svr-ies-ce-lava:~$ dpkg -l | grep lava ii lava 2020.07.0002.g44e83009c+10+buster all Linaro Automated Validation Architecture metapackage ii lava-common 2020.07.0002.g44e83009c+10+buster all Linaro Automated Validation Architecture common ii lava-coordinator 2020.07.0002.g44e83009c+10+buster all LAVA coordinator daemon ii lava-dev 2020.07.0002.g44e83009c+10+buster all Linaro Automated Validation Architecture developer support ii lava-dispatcher 2020.07.0002.g44e83009c+10+buster all Linaro Automated Validation Architecture dispatcher ii lava-dispatcher-host 2020.07.0002.g44e83009c+10+buster all LAVA dispatcher host tools ii lava-server 2020.07.0002.g44e83009c+10+buster all Linaro Automated Validation Architecture server ii lava-server-doc 2020.07.0002.g44e83009c+10+buster all Linaro Automated Validation Architecture documentation ii lavacli 0.9.5-1 all LAVA XML-RPC command line interface As specified in https://stackoverflow.com/questions/3323001/what-is-the-maximum-recursion-d… should we try to increase python recursion limit to overcome this? Thanks, Hemanth.

4 years, 7 months

2
6
0 0

lavapdu-client throwing error

by P T, Sarath

Hi，Team, I want to control device power on/off/reboot by lavapdu ,but when I run “/usr/bin/pduclient --daemon 134.86.60.229 --hostname 134.86.254.45 --command reboot --port 10” Error sending command, wrong daemon hostname? Can you help me solve this problem? Pdudaemon run on the lava-server. Below giving the configuration file for pduclient. { "daemon": { "hostname": "0.0.0.0", "port": 16421, "dbhost": "127.0.0.1", "dbuser": "pdudaemon", "dbpass": "pdudaemon", "dbname": "lavapdu", "retries": 5, "logging_level": "INFO" }, "pdus": { "192.168.10.2": { "driver": "apc9210" }, "192.168.10.3": { "driver": "apc7952", "telnetport": 5023 }, "192.168.10.4": { "driver": "apc7952" }, "192.168.10.5": { "driver": "apc8959", "this": "that", "something": "else" }, "192.168.25.52": { "driver": "apc7952" } } } Regards Sarath P T

4 years, 7 months

2
1
0 0

Error encounterd while using u-boot-ums deploy method

by DAS, BHARGAV

Hi Lava users, I am trying to use the u-boot-ums deploy method. I have taken reference from this job : https://staging.validation.linaro.org/scheduler/job/277518/definition While submitting the job I am getting the following error: Job error: None of the deployment strategies accepted your deployment parameters, reasons given: overlay: "to" parameter is not "overlay" docker: 'docker' not in the device configuration deploy methods download: "to" parameter is not "download" downloads: "to" parameter is not "downloads" qemu-nfs: "nfs" is not in the device configuration deploy methods images: "to" parameter is not "tmpfs" iso: "to" was not in parameters, or "to" was not "iso-installer" fastboot: "to" parameter is not "fastboot" flasher: 'flasher' not in the device configuration deploy methods fvp: 'to' was not fvp lxc: "to" parameter is not "lxc" nbd: "to" parameter is not "nbd" nfs: "to" parameter is not "nfs" removable: "media" was not "sata", "sd", or "usb" vemsd: "to" parameter is not "vemsd" mps: "mps" was not in the device configuration deploy methods musca: "musca" was not in the device configuration deploy methods ssh: "to" parameter is not "ssh" tftp: "to" parameter is not "tftp" uboot-ums: "u-boot-ums" was not in the device configuration deploy methods" recovery-mode: 'recovery' not in the device configuration deploy methods uuu: "to" parameter is not "uuu" Please check the attached yaml file (u-boot-ums-def.yaml). ? Regards, Bhargav

4 years, 7 months

3
5
0 0

is LAVA supports "Appium (http://appium.io/docs/en/about-appium/intro/) ?

by koti koti

Hi, Is LAVA Test Framework supports Appium? ( http://appium.io/docs/en/about-appium/intro/)? Like how the Robot Test framework supports Appium ? ( https://www.youtube.com/watch?v=_Z2QMrUA2cg) [image: image.png] Regards, Koti

4 years, 8 months

2
2
0 0

About --init in docker library.

by Larry Shen

Hi, I saw this change "docker: run containers with an init system": https://git.lavasoftware.org/lava/lava/-/commit/e0bfef019992f9032d87e9edf9f… This makes UUU container function which directly mount "/dev" won't work, see this: https://github.com/moby/moby/issues/37645 If possible this could be a optional one? You know, user don't need it if he just run one process in one container & set that process as PID1. Furthermore, even user start multiple process in one container, he still could use some like next to fix in its dockerfile. ENV TINI_VERSION v0.18.0 ADD https://github.com/krallin/tini/releases/download/${TINI_VERSION}/tini /tini RUN chmod +x /tini ENTRYPOINT ["/tini", "--"] CMD ["/root/entrypoint.sh"]

4 years, 8 months

1
2
0 0

Ask plan for docker test shell.

by Larry Shen

Hi, I saw something like "LAVA_HARD_RESET_COMMAND" was added to environment. Yes, the test action could use this command to reboot the device now, it's useful. But, after the command sent, the code in container still need to handle something like next: "Expect press any key to continue" "Press any key" "Expect login prompt" "Login" Etc...... But, this exactly the same code what lava have do in a lots of python files located in "lava_dispatcher/actions/boot". My question is: do you think it's possible for user code in "docker-test-shell" action directly send any command or use any protocol to tell lava code(maybe a listener or something else) to help to do these things, then after done, the user code in docker test shell continue to execute its own stuff? You know, this could reuse existed lava code as much as possible. I just want to know if you have plan for this? Thanks.

4 years, 8 months

2
2
0 0

fastboot in docker support

by Stephen Lawrence

Hi, I have some questions about the fastboot/adb in docker support I hope you can help with. Use case is for android 10 aosp testing with LAVA 2020.05. Thanks to Antonio's presentation and draft documentation I have simple fastboot host to DUT communication working for a u-boot based arm64 board. I am now trying to apply an existing flash process, which uses a script on the host to send fastboot cmds, into a LAVA job. I can see how fastboot --set-active, reboot and flash commands all have equivalent controls in a 'deploy to fastboot docker' LAVA job section. Do equivalents exist for the fastboot oem format, oem erase, format and erase commands or is there a way to insert them in the deploy? Expecting that will take some engineering work, in parallel I wanted as a stop gap to try running the flash script from a LAVA job. So people could work on the testing side whilst I resolved the deploy section. Antonio suggested trying to do that from the test section I recall. To do that I face two issues: 1) The build artifacts are on a local volume rather than an artifact server so I need to get them into the docker container in an automated way. Is there a way to either mount a local volume or file list into the container without asking LAVA to deploy them? As an experiment I tried using the docker image manipulation added in 2020.04 to do this. There I hit a problem with the current implementation. It seems the 'deploy to downloads' implementation does not check for a local image first, as the other docker support does, before trying to pull the image. So I get an error when the pull fails: https://lava.genivi.org/scheduler/job/961#L24 2) The job needs to be able to boot the DUT, interrupt u-boot and start fastboot so the host has something to communicate with once the test section is reached. I can achieve that in a horrible hacky way by having a deploy section with a simple single flash image (dtbo say) and using the reboot controls to get the board to reboot into fastboot to await the flash script being run from the test section, but I expect there is a better way. Any ideas? Regards Steve

4 years, 8 months

4
38
0 0

tee support breaking job with Bug error: 'tee'

by Stephen Lawrence

Hi, Taking the current master branch head (0f6e89e3) I find my health checks that use u-boot tftboot support are now failing with the following: start: 2.2 bootloader-overlay (timeout 00:05:00) [common] Traceback (most recent call last): File "/usr/lib/python3/dist-packages/lava_dispatcher/action.py", line 245, in run_actions new_connection = action.run(connection, action_max_end_time) File "/usr/lib/python3/dist-packages/lava_dispatcher/actions/boot/__init__.py", line 454, in run tee_addr = self.job.device["parameters"][self.bootcommand]["tee"] KeyError: 'tee' Example job: https://lava.genivi.org/scheduler/job/1160 I've not combed through the code in detail but it looks like it is related to the recent tee merge: https://git.lavasoftware.org/lava/lava/-/commit/f18ca091e61da31159cd72a0030… That appeared to introduce an optional feature which my jobs do not make use. Am I missing something? Regards Steve

4 years, 8 months

2
2
0 0

settings.conf not available in /etc/lava-server

by Koturappa, Hemanth

Hello Lava-Users, When we trying to setup new instance of LAVA server(2020.07) facing the issue of settings.conf file not available after installation at /etc/lava-server/ . Following the steps mentioned as in https://docs.lavasoftware.org/lava/installing_on_debian.html .Request on guidance If I am missing something. Package Installation Log : https://pastebin.com/B7K0gXBp hemanth@hemanth:~$ dpkg -l | grep lava ii lava-common 2020.07+10+buster all Linaro Automated Validation Architecture common ii lava-coordinator 2020.07+10+buster all LAVA coordinator daemon ii lava-dispatcher 2020.07+10+buster all Linaro Automated Validation Architecture dispatcher ii lava-dispatcher-host 2020.07+10+buster all LAVA dispatcher host tools ii lava-server 2020.07+10+buster all Linaro Automated Validation Architecture server ii lava-server-doc 2020.07+10+buster all Linaro Automated Validation Architecture documentation hemanth@hemanth:~$ ls -la /etc/lava-server/ total 44 drwxr-xr-x 5 root root 4096 Jul 22 10:30 . drwxr-xr-x 148 root root 12288 Jul 22 10:30 .. drwxr-xr-x 5 lavaserver lavaserver 4096 Jul 22 10:30 dispatcher-config drwxr-xr-x 2 lavaserver lavaserver 4096 Jul 9 21:03 dispatcher.d -rw-r--r-- 1 root root 900 Jul 9 20:28 env.yaml -rw-r--r-- 1 root root 589 Jul 9 20:28 lava-logs -rw-r--r-- 1 root root 719 Jul 9 20:28 lava-master -rw-r--r-- 1 root root 496 Jul 9 20:28 lava-server-gunicorn drwxr-xr-x 2 root root 4096 Jul 22 10:30 settings.d Installing on Debian 10 Buster Host hemanth@hemanth:~/mentor-lava-sources/mentor-lava$ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL=https://bugs.debian.org/ Thanks, Hemanth.

4 years, 8 months

3
5
0 0

LTP and some other tests in QEMU

by 黄璐

4 years, 8 months

1
0
0 0

Run shell commands in a docker job

by baptiste.billard＠e.email

Dear lava-users, I'm intern at /e/ foundation and working on using LAVA to test our OS updates. We are trying to configure our system in order to use the recent feature allowing the use of docker instead of LXC containers. On this point we are grateful to the developpers for adding this possibility because we were having problems with LXC. Now we are having issues because we can't flash our OS through fastboot, we have to use adb sideload with .zip archives. By the way, we can't do it through the classic deploy section. We came with the idea of just flashing a twrp recovery partition via the deploy section using fastboot, and then trying to run shell commands in the test section to be able to use adb sideload and install our ROM. For the moment as you can see in the job we didn't add all the shell commands because we already have some problems with this simple try. The objective would be to pass this booting into recovery step and then try to continue with adb sideload. I've also joined the logs and the device and device type dictionaries. I would like to have your opinion and advices on what we are trying to achieve. Best regards, Baptiste and the /e/ team

4 years, 8 months

1
0
0 0

Execute u-boot pytest with LAVA

by Philippe BEGNIC

Hello everyone, I would like to integrate the u-boot tests suite (pytest) in lava. ( https://github.com/u-boot/u-boot/tree/master/test/py) We are now executing the test suite manually, using a host machine and the DUT. The u-boot tests suite is installed on a host computer and the DUT is "stopped" in uboot environment. The host computer execute the "u-boot pytest" framework, commands are sent to the DUT and tests results are collected to the host computer. It is a "semi automatic" tests and I would like to do a full automation using LAVA. I plan to use multinode jobs, one job instances for the DUT and another one for the remote host computer. So, I would like to know if such tests have already been craeted in LAVA, and if someone could give me advice on this tests implementation. My Lava version is: 2020.06 Best regards Philippe Begnic STMicroelectronics

4 years, 8 months

2
2
0 0

lxc errors after updating from 2019.12 to 2020.01

by Alexander Moore

Hello, We are wanting to update to a more recent LAVA docker release, we've been at 2019.12 since it was released. Our configuration relies on lxc, and after moving to 2020.01 all of our test jobs hit the error "lxc container 'lxc-test-17071' already exists" very early on (17071 is the test job number). I've pasted our device configuration, test job, and log output in the below pastebin. What should we do to keep our LAVA jobs working with the 2020.01 release and beyond? https://pastebin.com/UQixc6RS Thanks, Alex This message and any attachments may contain confidential information from Cypress or its subsidiaries. If it has been received in error, please advise the sender and immediately delete this message.

4 years, 8 months

3
7
0 0

Tee support for armv7?

by Larry Shen

Hi, For imx armv7 series board, tee is default not built in, there is a separate file there to play the role. I'm not sure for next scenario, if LAVA could handle it with "method: u-boot commands: nfs"? Could you give some guide? setenv autoload no setenv initrd_high 0xffffffff setenv fdt_high 0xffffffff dhcp setenv serverip 10.192.244.84 tftp 0x12000000 trial/zImage-imx6qsabresd.bin tftp 0x18000000 trial/zImage-imx6q-sabresd.dtb tftp 0x20000000 trial/uTee-6qsdb tftp 0x12C00000 trial/ramdisk.cpio.gz.uboot bootm 0x20000000 0x12C00000 0x18000000 If not, if you have buffer to add the support? Or we can submit a MR for review?

4 years, 9 months

1
1
0 0

Re: [Lava-users] [EXT] Re: docker shell cannot handle adbd.

by Larry Shen

Thanks Antonio for the clarify. A side question: For docker test shell, if possible add more docker options for user? E.g. bind mount, etc. A scenario is: If we have some code needed when test, currently, we could just inject it into docker image when do docker build, or when test git clone the code from network. You know docker test shell use `--rm`, means every time, we need to git clone it, or if a small changes we need to build the image. A bind mount there to mount our code may make things easier for us? -----Original Message----- From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of lava-users-request(a)lists.lavasoftware.org Sent: Saturday, June 6, 2020 8:00 PM To: lava-users(a)lists.lavasoftware.org Subject: [EXT] Lava-users Digest, Vol 22, Issue 7 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: [EXT] Re: docker shell cannot handle adbd. (Antonio Terceiro) ---------------------------------------------------------------------- Message: 1 Date: Fri, 5 Jun 2020 09:26:18 -0300 From: Antonio Terceiro <antonio.terceiro(a)linaro.org> To: lava-users(a)lists.lavasoftware.org Subject: Re: [Lava-users] [EXT] Re: docker shell cannot handle adbd. Message-ID: <20200605122618.GA359587(a)linaro.org> Content-Type: text/plain; charset="us-ascii" On Fri, Jun 05, 2020 at 07:06:16AM +0000, Larry Shen wrote: > Hi, Milosz, > > Maybe I understand wrong, but I already see there is code like next to > add dynamic device node to docker container. > > I tried it in manual, adb find devices after a new device node added > with next code. But I don't see the docker shell try to call it with > some way. What's the aim of next code if you did not want to use it? > Could you double confirm internal maybe some guys is handling it, but > just in process? Could you do me a favor inform me your plan if my > guess is true? > > I don't think people could switch from lxc to docker on android if > this not support, maybe my environment wrong or anything else? Yes, you are right. The way the docker test shell currently works won't support such a use case. First, there was an issue with the udev rules being too strict, which was recently fixed and will be in the next release: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavas… This issue that you mention also needs to be fixed; I created an issue to track and I will work on it: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavas…

4 years, 9 months

3
8
0 0

minimal boot and mutiple deploy

by Koturappa, Hemanth

Hello Lava-Users, For minimal boot setup should the dispatcher with which target is configured should have apache server setup configuration ?Having the Lava server version of 2019.11. When trying to pull test suites from the dispatcher with overlay mechanism facing http not found error during job execution. --2020-06-24 14:50:07-- http://xx.xx.xx.31/tmp/21866/compress-overlay-mmk3i76o/overlay-1.4.2.4.tar.… Connecting to xx.xx.xx.31:80... connected. HTTP request sent, awaiting response... 404 Not Found Also needed suggestion on Presently trying with the multi deploy mechanism where in 1st deploy boot test method we boot with nfs boot and wget the latest wic image and write that image to hard disk as test case. In the scenario of writing of Image fails how should we exit from job execution without going to 2nd deploy boot test Thanks, Hemanth.

4 years, 9 months

1
0
0 0

Docker in Docker support, again

by Paul Sokolovsky

Hello, Situation with running Docker containers inside the official Docker-based LAVA setup (https://git.lavasoftware.org/lava/pkg/docker-compose) was already discussed at least once recently. LAVA starts to offer more and more convenient usages of Docker containers to extend its functionality (e.g. https://connect.linaro.org/resources/ltd20/ltd20-304/), and people start to leverage it. For docker-compose based setup, that effectively means running Docker containers inside the docker-compose, and that currently doesn't work. Another reason for raising this matter again are the apparent plans to migrate components of the production LAVA setup as run by Linaro (https://validation.linaro.org/) to Docker-based setup. The concern is that if Docker-in-Docker scenario is not explicitly accounted and planned for, then there will be a regression due to this switchover. So, I posted https://git.lavasoftware.org/lava/pkg/docker-compose/-/issues/7 with more detailed discussion, and would be ready to follow up with a patch (we just need to decide what kind of patch, please the proposed options there). -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

4 years, 10 months

2
3
0 0

Upgrading LAVA while preserving database

by Vincent Wan

Hi, What is the procedure to follow in order to upgrade LAVA to a new release while preserving the test results database? I am using the docker-based setup. I tried > > sudo tar cvzf lava-server-pgdata-backup.tgz > /var/lib/docker/volumes/lava-server-pgdata > <wipe away old LAVA, rebase to latest> > sudo tar xvzf lava-server-pgdata-backup.tgz -C > /var/lib/docker/volumes/lava-server-pgdata But the old results don't seem to show up in the UI after the upgrade. Also the user accounts, settings, etc. are gone, and it'd have been nice to keep them. Thanks, Vincent -- ----------------------- Vincent Wan Linaro.org

4 years, 10 months

2
3
0 0

docker shell cannot handle adbd.

by Larry Shen

Hi, guys, I have a job like next: - test: timeout: minutes: 10 docker: image: terceiro/android-platform-tools definitions: - from: inline name: smoke-case path: inline/install-google-fastboot.yaml repository: metadata: format: Lava-Test Test Definition 1.0 name: smoke-case-run description: Run smoke case run: steps: - env - sleep 10 - adb devices - adb root - sleep 10 - adb devices - lava-test-case get-release-version --shell adb shell getprop ro.vendor.build.fingerprint It output as next: + sleep 10 + adb devices * daemon not running; starting now at tcp:5037 * daemon started successfully List of devices attached 040c41d4d72d7393 device + adb root + sleep 10 + adb devices List of devices attached + lava-test-case get-release-version --shell adb shell getprop ro.vendor.build.fingerprint <LAVA_SIGNAL_STARTTC get-release-version> Received signal: <STARTTC> get-release-version error: device '040c41d4d72d7393' not found <LAVA_SIGNAL_ENDTC get-release-version> Received signal: <ENDTC> get-release-version <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=get-release-version RESULT=fail> Received signal: <TESTCASE> TEST_CASE_ID=get-release-version RESULT=fail You know "adb root" will make usb bus change during run, so could docker shell handle this? How can I make above work? Thanks.

4 years, 10 months

3
5
0 0

Unable to run commands on U-boot on Renesas board Using LAVA

by Nagendra Singamsetti

Hello Team, With the existing JLink.py library i have modified and able to flash multiple *.bin files in single instance/Job. I have used method : Jlink in boot: But On the Renesas boards, After flash the binaries through Debugger Say JLink, Will get U-boot prints at ttyACM0. I can see the prints through ser2net telnet host. Q1. How to send command at uboot level while using JLink boot method. I need to *send run xa_boot from uboot prompt: =>* *Below is sample Job description :* - boot: method: jlink prompts: ["=>"] commands: ["run xa_boot"] timeout: minutes: 5 *i am getting following error :* *Invalid job definition:* extra keys not allowed @ data['actions[1]']['boot']['jlink']['prompts'] I tried with out prompts and commands key values in job description Job terminated once the flash has done. Attached logs for reference: Looking forward for your kind response Thanks Regards Nagendra S

4 years, 10 months

3
3
0 0

Request : Code Flow

by Nagendra Singamsetti

Hello Team, To get better understanding the lava frame work , Can any one share me the code flow diagram for LAVA. I have gone through the available Doc's in lava, but i did not understand the flow properly. thanks & Regards Nagendra S

4 years, 10 months

2
1
0 0

Unable to execute login command while booting with LAVA

by Nagendra Singamsetti

Hi Team, I am using U-boot method to boot up to linux. But at the end of booting means before gets the login prompt it got hanged at here.. [ 3.759014] Console: switching to colour dummy device 80x30[?25lfbv - The Framebuffer Viewer/root/images/renesas_logo-800x480.jpg800 x 480[?25hWelcome to Buildroot after 2 minutes got *buildroot login: [ 90.929835] random: crng init done * due to this Lava did not fetch "root" string and unable to login. And i have seen stange string in lava while booting [?25h . I am able to boot manually (with out lava) with out an issue. And i did not get [?25h string .. How to avoid this problem .Attaching job description/device dictionary files . [ 2.837060] Run /sbin/init as init process�Starting logging: OKread-only file system detected...doneStarting network: OKWed Oct 31 09:00:00 UTC 2018[ 3.759014] Console: switching to colour dummy device 80x30[?25lfbv - The Framebuffer Viewer/root/images/renesas_logo-800x480.jpg800 x 480[?25hWelcome to Buildrootbuildroot login: [ 90.929835] random: crng init done

4 years, 10 months

2
2
0 0

UART connection issue with LAVA

by Nagendra Singamsetti

Hi, The Renesas board I am using behaves as a USB to UART adapter through /dev/ttyACM0 at 115200bps. Created the board instance in device dictionary file as: {% extends 'rza1h.jinja2' %} {% set board_id = '0000000000001' %} {% set console_device = 'ttyACM0' %} {% set baud_rate = baud_rate|default(115200) %} {% set usb_mass_device = '/dev/serial/by-id/usb-Renesas_Electronics_Corporation_Renesas_RSK_USB_Serial_Port_0000000000001-if00' %} {% set connection_list = ['usb0'] %} {% set connection_tags = {'usb0': ['primary', 'telnet']} %} {% set connection_commands = {'usb0': 'telnet localhost 2000'} %} With the above configuration, Dispatcher(Remote worker) flashes the board through JLink.And I can see flashing log in the Job console. But Even i specified the UART connection like (/dev/ttyACM0, 115200bps). I am not getting the u-boot logs on /dev/ttyACM0. Did i miss any other configuration to add in device dictionary???. Manaually, I can able to see uboot prints on the console through minicom with /dev/ttyACM0 with 115200bps. Attaching logs for reference. Thanks Regards Nagendra S

4 years, 11 months

2
2
0 0

Fwd: [EXT] Test jobs to boot the targets through trace32

by Nagendra Singamsetti

---------- Forwarded message --------- From: Nagendra Singamsetti <nag.singam91(a)gmail.com> Date: Fri, May 22, 2020 at 8:58 AM Subject: Re: [EXT] [Lava-users] Test jobs to boot the targets through trace32 To: Andrei Gansari <andrei.gansari(a)nxp.com> Hi Andrei, Good Morning !! *lava-dispatcher machine did not reach the serial on the device* I have debug the issue. Issue is telnet socket connection is not up. Now i am able to flash Renesas board using Jlink Debugger through LAVA. Attached job [image: lava_jlink_uboot_download.png] [image: lava_jlink_uboot_flash.png] Thanks!! for your good time to debug this issue. Now i am able to flash U-boot @specific offset say-0x18000000. Need to flash .dtb,Kernal & rootfs. Should i run again with different Job's or Can i run in single Job?? . Can you Please share your thoughts !! Regards Nagendra S On Thu, May 21, 2020 at 5:45 PM Nagendra Singamsetti <nag.singam91(a)gmail.com> wrote: > Hi Andrei, > Thanks for your kind response :) :) > > 1. > *Is your board flashed with the desired uboot? You can check by erasing > the flash and then running lava, the desired uboot should be flashed on the > board.* > Ans. Using lava, i am unable to flash with u boot also. As you mention I > have erased the flash up to 0 0x2000000 and tried again getting same > issue.error_msg: Invalid job data: ["Invalid device configuration - missing > 'commands'"]. > > 2.* Can you lava-dispatcher machine reach the serial on the device?* > Ans. In rza1h.jinja2, device-type file: i have added following commands to > open serial console > {% set console_device = console_device|default("ttyACM0") %} > {% set baud_rate = baud_rate|default(115200) %} > {% set bootloader_prompt = bootloader_prompt|default("=>") %} > > But i don't know* lava-dispatcher** machine reach the serial on the > device* or not. Due to job immediately terminated. > *Manually i am able to flash through JLink with following commands* : > JLinkExe -speed 15000 -if JTAG $JTAGCONF -device R7S721001 -CommanderScript > load_spi_uboot.txt > > *load_spi_uboot.txt contains following:* > rx 100 > exec SetSkipProgOnCRCMatch=0 > > // > // Download application into QSPI flash > // > > loadbin u-boot.bin,0x18000000 > //verifybin u-boot.bin,0x18000000 > > exit > > > 3. board_id:* '{{ board_id|default('0000000000') }}',usb_vendor_id: > '1366',usb_product_id: '0101' refers to JLink connected usb right. Can i > change directly in the device-type .jinja2 file.* > > I am very thankful, if you can share your sample device jinja2 , > device-type (jinja2 file) and working job description file. > I am just stuck with this issue issue.error_msg: Invalid job data: > ["Invalid device configuration - missing 'commands'"] from last 5 day's. i > gone through all the mail chain from lava-users but did not get proper > information.Don't know how to debug this issue. > Your presence and input is more valuable for me . > > I am attaching used job description and device& device-type .jinja files > for your reference. > > > > On Wed, May 20, 2020 at 4:04 PM Andrei Gansari <andrei.gansari(a)nxp.com> > wrote: > >> Hello Nagendra, >> >> >> >> Looks like *error_msg*: Invalid job data: ["Invalid device configuration >> - missing 'commands'"] is issued from serial.py so the validation reached >> executing serial commands. >> >> >> >> 1. Is your board flashed with the desired uboot? You can check by >> erasing the flash and then running lava, the desired uboot should be >> flashed on the board. >> 2. Can you lava-dispatcher machine reach the serial on the device? >> 3. Most likely it’s this pattern in job*.yaml it should look for the >> printed uboot header of prompt when the board is reset. The configuration >> below is used by Zephyr RTOS tests. >> >> - test: >> >> monitors: >> >> - name: tests >> >> * start: Running test suite common_test* >> >> * end: PROJECT EXECUTION SUCCESSFUL* >> >> * pattern: '(?P<result>(PASS|FAIL)) - (?P<test_case_id>.*)\.'* >> >> fixupdict: >> >> PASS: pass >> >> FAIL: fail >> >> >> >> Regards, >> >> Andrei G. >> >> >> >> *From:* Nagendra Singamsetti <nag.singam91(a)gmail.com> >> *Sent:* Tuesday, May 19, 2020 8:01 PM >> *To:* Andrei Gansari <andrei.gansari(a)nxp.com>; >> lava-users(a)lists.lavasoftware.org >> *Cc:* andrei.gansari(a)linaro.org >> *Subject:* Re: [EXT] [Lava-users] Test jobs to boot the targets through >> trace32 >> >> >> >> *Caution: *EXT Email >> >> Hi Andrei, Team, >> >> >> >> Issue is solved this is because of lava-server & remote worker version >> mismatch. I tried to boot the DUT (RZA1_RSA , Renesas) Using the >> rza1h.jinja2 file & job description with Segger Jlink debugger . I am >> getting following issue: >> >> - >> - *error_msg*: Invalid job data: ["Invalid device configuration - >> missing 'commands'"] >> - *error_type*: Job >> >> [image: renesas_jlink_Invalid_device_configuration.png] >> >> I am looking forward for your kind response.. >> >> >> >> thanks >> >> >> >> Regards >> >> Nagendra S >> >> >> >> >> >> On Tue, May 19, 2020 at 8:12 PM Nagendra Singamsetti < >> nag.singam91(a)gmail.com> wrote: >> >> Hello Andrei , Team, >> >> To get hands on knowledge, I have tried to boot Renesas images using >> JLink & Renesas - RZA1_RSA ver2 board on QSPI flash. >> >> I took frdm-k64f.janja2 file as a reference created *rza1h.jinja2* as a >> device-type. And added device as a *renesas_worker1(DUT)* under >> device-type *rza1h.* And connected to remote worker. >> >> On Remote worker, Segger Jlink debugger is connected to the DUT with jtag >> cable. >> >> >> >> But while submitting Job definition i am getting following error. >> >> >> >> [image: renesas_jlink_job_error.png] >> >> >> >> Attaching Job files and device-type file for reference. >> >> First time i am booting the hardware with Jlink using LAVA framework. >> Please help me out to debug this issue. >> >> >> >> Thanks >> >> >> >> Regards >> >> Nagendra S >> >> >> >> >> >> >> >> On Mon, Apr 27, 2020 at 5:28 PM Andrei Gansari <andrei.gansari(a)nxp.com> >> wrote: >> >> Please have a look at my pull requests: >> >> >> >> https://git.lavasoftware.org/lava/lava/-/merge_requests/608/diffs >> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavas…> >> - script changes >> >> https://git.lavasoftware.org/lava/lava/-/merge_requests/758/diffs >> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavas…> >> - job sample >> >> >> >> With JLink you need to install Segger’s software on the server where Lava >> dispatcher resides (in case you have multiple Lava servers). >> >> https://www.segger.com/downloads/jlink/#J-LinkSoftwareAndDocumentationPack >> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.segge…> >> >> >> >> >> >> Regards, >> >> Andrei >> >> >> >> *From:* Nagendra Singamsetti <nag.singam91(a)gmail.com> >> *Sent:* Monday, April 27, 2020 12:42 PM >> *To:* Andrei Gansari <andrei.gansari(a)nxp.com> >> *Cc:* andrei.gansari(a)linaro.org; lava-users(a)lists.lavasoftware.org >> *Subject:* Re: [EXT] [Lava-users] Test jobs to boot the targets through >> trace32 >> >> >> >> *Caution: *EXT Email >> >> Hi Andrei, >> >> >> >> Wonderful!!, >> >> Thanks for your time .. >> >> I need bit support from you, don't mine :) ,Can you please share your >> Jink scripts. I will use these as a reference will write comparable boot >> method for trace32 . >> >> >> >> And if you can, Please share the appropriate Doc (link) to >> setup(interface) other software's in Lava server. Setup Jlink with Lava >> server also fine. >> >> >> >> >> >> Regards >> >> Nagendra S >> >> >> >> On Mon, Apr 27, 2020 at 2:10 PM Andrei Gansari <andrei.gansari(a)nxp.com> >> wrote: >> >> Hello Nagendra, >> >> >> >> JLink was added as most NXP mcus use this interface, there is no support >> for T32 in Lava as far as I know. >> >> Even if they use the same JTAG interface standard, Segger and Lauterbach >> use different hardware and software to interact. >> >> I’ve used JLinkExe command line software (from Segger) to control the >> debugger, in the case of T32 you will probably need to use Lauterbach’s >> Trace32 command line software + scripts, such as: >> https://stackoverflow.com/questions/24883140/controlling-trace32-via-comman… >> <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackover…> >> >> Haven’t used Trace32 GUI software for some years, never used the command >> line. >> >> >> >> You can probably create a flashing script starting form JLink scripts, >> you need to: >> >> - setup trace32 software on your Lava server >> - learn how to use the command to flash your board using a cmm script >> - change JLink scripts with T32 commands and cmm script generation >> - pull request your changes so others can benefit 😊 >> >> >> >> Andrei Gansari >> >> >> >> *From:* Lava-users <lava-users-bounces(a)lists.lavasoftware.org> *On >> Behalf Of *Nagendra Singamsetti >> *Sent:* Saturday, April 25, 2020 9:05 AM >> *To:* Kumar Gala <kumar.gala(a)linaro.org>; andrei.gansari(a)linaro.org >> *Cc:* lava-users(a)lists.lavasoftware.org >> *Subject:* [EXT] [Lava-users] Test jobs to boot the targets through >> trace32 >> >> >> >> *Caution: *EXT Email >> >> Hi Kumar, Andrei >> >> >> >> From the previous lava- mailing list i have seen that you people >> addressed jlink debugger information as like this : >> >> *On Thu, Jan 23, 2020 at 7:33 PM Andrei Gansari <andrei.gansari at nxp.com <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lav…>>* >> >> >>* wrote:* >> >> >> >> >> >>* From the screenshot it looks like you have a version of LAVA that does* >> >> >>* not support jlink boot method.* >> >> >> >> >> >>* JLink was added in version 2019.10-1* >> >> >> >> >> >> >>* On Tue, Nov 26, 2019 at 2:36 PM Andrei Gansari <andrei.gansari at nxp.com <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lav…>>* >> >> >>* wrote:* >> >> >> >> >> >>* I’ve tested lava+jlink on Cortex M with both onboard debugger and* >> >> >>* external debugger, like the one you referenced.* >> >> >> >> >> >>* You should change the following if needed:* >> >> >> >> >> >> >> >> >> >> >> >>* address:* >> >> >> >> >> >>* *0x00000000** >> >> >> >> >> >>* options:* >> >> >> >> >> >>* - '-device *MK64FN1M0xxx12'** >> >> >> >> >> >>* - '-if SWD'* >> >> >> >> >> >>* - '-speed 4000'* >> >> >> >> Can you please let me know, whether the latest lava version can support trace32 boot method instead jlink/cmsis-dac. trace32 debugger tool is designed by lauterbach and it is licensed one. >> >> I am bit afraid whether this support is available from lava server or not as Jlink support added recently. >> >> https://www2.lauterbach.com/pdf/app_t32start.pdf <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww2.laut…> >> >> We need trace32 debugger support as we are using cortex-M55 processor operations over here. >> >> I am looking forward your kind support >> >> >> >> thanks >> >> Regards >> >> Nagendra S >> >>

4 years, 11 months

1
0
0 0

About pdu script.

by Peter Lucas

Sorry, I missed title, send again. Hello, Milosz, Another question: I see your documentation suggest to use pdudaemon. But I had a look for you validation lava lab: https://validation.linaro.org/scheduler/device/hi6220-hikey-r2-02/devicedict, I see you use /usr/local/lab-scripts/snmp_pdu_control I want to know why your lab not use the one which you suggest? I had a look for pdudaemon, found it won't wait there until PDU operation finish. Will this have any issue? Will next logic start before the pdu really finish the operation?

4 years, 11 months

2
3
0 0

Test jobs to boot the targets through trace32

by Nagendra Singamsetti

Hi Kumar, Andrei >From the previous lava- mailing list i have seen that you people addressed jlink debugger information as like this : *On Thu, Jan 23, 2020 at 7:33 PM Andrei Gansari <andrei.gansari at nxp.com <https://lists.lavasoftware.org/mailman/listinfo/lava-users>> *>>* wrote: *>>>>* From the screenshot it looks like you have a version of LAVA that does *>>* not support jlink boot method. *>>>>* JLink was added in version 2019.10-1* >>* On Tue, Nov 26, 2019 at 2:36 PM Andrei Gansari <andrei.gansari at nxp.com <https://lists.lavasoftware.org/mailman/listinfo/lava-users>> *>>* wrote: *>>>>* I’ve tested lava+jlink on Cortex M with both onboard debugger and *>>* external debugger, like the one you referenced. *>>>>* You should change the following if needed: *>>>>>>>>* address: *>>>>* *0x00000000* *>>>>* options: *>>>>* - '-device *MK64FN1M0xxx12'* *>>>>* - '-if SWD' *>>>>* - '-speed 4000'* Can you please let me know, whether the latest lava version can support trace32 boot method instead jlink/cmsis-dac. trace32 debugger tool is designed by lauterbach and it is licensed one. I am bit afraid whether this support is available from lava server or not as Jlink support added recently. https://www2.lauterbach.com/pdf/app_t32start.pdf We need trace32 debugger support as we are using cortex-M55 processor operations over here. I am looking forward your kind support thanks Regards Nagendra S

4 years, 11 months

4
10
0 0

Question about serial.

by Peter Lucas

Dear Sir/Madam, I'm new to LAVA. I'm still in initial stage to use lava in our farm. I use customized board with Qualcomm's chip. Recently I met a question, a very simple job, sometimes when I start to operate uboot, the serial have chance to be closed. They I set retry in lava job, let it retry a lots of times, but looks never successfully open the serial again. But, after job finish, I quickly open the serial in manual, it's ok! I search your code a lot, and found in shell.py there is one comments, I want to know is this the reason that I failed to retry for serial? When will you fix it? *# FIXME: deliberately closing the connection (and starting a new one) needs to be supported.* *Cheers,* *Peter*

4 years, 11 months

2
6
0 0

Docker device basic setup

by Saheer Babu

Hi Lava folks, I am new to LAVA and trying to get some basic understand of lava. I am facing issues while I trying to set up a docker device in lava following the doc: https://lava.readthedocs.io/en/latest/admin/basic-tutorials/instance/instal… Steps followed: 1. I have installed Debian VM on my mac book pro. 2. Installed lava: https://lava.readthedocs.io/en/latest/admin/basic-tutorials/instance/instal… * Enabled lava site in apache “Production releases” https://docs.lavasoftware.org/lava/installing_on_debian.html (Btw, this step seems to be missing) * Config like “ALLOW_HOSTS<https://docs.lavasoftware.org/lava/advanced-installation.html?highlight=all…>”, CSRF etc: (a * Created one super user: https://lava.readthedocs.io/en/latest/admin/basic-tutorials/instance/config… * Created a token (for lavacli): sudo lava-server manage tokens add --user root 1. Setup docker device for running tests: https://lava.readthedocs.io/en/latest/admin/basic-tutorials/device-setup/do… ( I am following command line using lava-cli) * $LAVACLI device-types add docker * $LAVACLI devices add --type docker --worker buster.localdomain docker01 * $LAVACLI devices dict set docker01 test.jinja2 (test.jinja2 contains {% extend "docker.jinja2" %} ) * $LAVACLI devices update --health UNKNOWN docker01 After step “3”, I have the following error: “Configuration Error: missing or invalid template.” I am assuming there is some pre-condition I am not meeting for docker device. How can I get some more debug information on this? Can you help? Cheers, Saheer Babu 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.

4 years, 11 months

2
2
0 0

(no subject)

by Peter Lucas

Hello, Milosz, Another question: I see your documentation suggest to use pdudaemon. But I had a look for you validation lava lab: https://validation.linaro.org/scheduler/device/hi6220-hikey-r2-02/devicedict, I see you use /usr/local/lab-scripts/snmp_pdu_control I want to know why your lab not use the one which you suggest? I had a look for pdudaemon, found it won't wait there until PDU operation finish. Will this have any issue? Will next logic start before the pdu really finish the operation?

4 years, 11 months

1
0
0 0

Need help for 2020.05 release.

by Larry Shen

Hi, We have a problem here needs your help, as it's critical to us, could you give some suggestion? Thanks in advance. You know, we submit a MR here about reset shell: https://git.lavasoftware.org/lava/lava/-/merge_requests/1023 It's nearly compatible from 2018.11 to 2020.04 release when we patch it in local, the only changes I remember is once upon a time you changed all "internal_pipeline" to "pipeline", so we had to follow the new name. But in yesterday's 2020.05 release, I saw this commit: https://git.lavasoftware.org/lava/lava/-/commit/eefeef1864cc055c48215169b61… In this commit, the test action no longer been added as before like next: def __init__(self, parent, parameters): super().__init__(parent) self.action = TestShellRetry() self.action.job = self.job self.action.section = self.action_type parent.add_action(self.action, parameters) It becomes next: @classmethod def action(cls, parameters): return TestShellRetry() Correspondingly, in parse.py, it becomes from next: action(pipeline, parameters) to next: action = cls.action(parameters) That means "parent pipeline" no longer been passed to next level pipeline, parse.py will responsible for low level action inject into pipeline. Above change is the key issue we encountered as in our "ResetTestShell" we need to reuse the parameters of "Boot" in same namespace, we need it to operate UBoot & Login again after device reset, like next: def __init__(self, parent, parameters): super().__init__(parent) boot_action_para = None for per_action in parent.actions: if per_action.parameters["namespace"] == parameters["namespace"]: if per_action.__class__.__base__.__name__ == "BootAction": boot_action_para = per_action.parameters self.action = TestShellLoop(boot_action_para) self.action.job = self.job self.action.section = self.action_type parent.add_action(self.action, parameters) You see we could get the "Boot" action from its parent action, thus we could get the boot action's parameters defined in job.yaml, then reconstruct the boot action, inject it as a internal action to our own test action. But now, we can't do it as parent action no longer be passed to low level action... Could you give me some suggestion on it, if any other way I could get the parameters of boot action when I'm in test action? Thanks again. Regards, Larry

4 years, 11 months

1
2
0 0

docker-compose: how to administrate a LAVA master from this?

by Philippe Mazet (OSS)

Hi, I am looking into https://git.lavasoftware.org/lava/pkg/docker-compose I have few questions about it: * Are there guidelines somewhere about how to administrate a "master only" instance run from this docker-compose? Like tutorials about creating/restoring a backup, periodic maintenance/cleanup, restart one of the containers idenpendantly, upgrade versions, etc... * Is there an easy way to inject a backup created from a previous instance? (backup created with pg_dump. Note that I am not psql expert at all...) * Is LAVA coordinator supported in this docker solution ? Many thanks, Philippe

4 years, 11 months

3
3
0 0

test

by Remi Duraffort

Hello, please skip this message. -- Rémi Duraffort LAVA Architect Linaro

4 years, 11 months

1
0
0 0

LTP included rootfs.cpio file for Qualcomm Snapdragon (arm64) series

by koti koti

Hi, I am looking for the LTP test suite included(inbuild) rootfs.cpio file for the Qualcomm Snapdragon (arm64) seris. Please can some one let me know as where can I find this .cpio file in Linaro's prebuild releases? Regards, Koti

4 years, 11 months

3
4
0 0

Re: [Lava-users] Evaluating return value of user_commands

by Tim Jaacks

Oh, the action indeed DOES cause an infrastructure error if it fails, my command simply did not return an error in case of a failure. Sorry for the noise! Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Schlachthofstrasse 20 21079 Hamburg Direct: +49 40 791 899 - 183 Fax: +49 40 791899 - 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com WE MAKE IT YOURS! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun -----Ursprüngliche Nachricht----- Von: Tim Jaacks Gesendet: Donnerstag, 30. April 2020 16:32 An: lava-users(a)lists.lavasoftware.org Betreff: Evaluating return value of user_commands Hello everyone, I am using a command action with pre-defined user_commands in the device dictionary for switching relays, as described here: https://master.lavasoftware.org/static/docs/v2/actions-command.html The return value does not seem to be evaluated, though. The test continues even if my user_command fails. I would assume that this causes an infrastructure failure, resulting in an incomplete job. Why is this not the case? Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Schlachthofstrasse 20 21079 Hamburg Direct: +49 40 791 899 - 183 Fax: +49 40 791899 - 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com WE MAKE IT YOURS! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun

4 years, 11 months

2
1
0 0

Evaluating return value of user_commands

by Tim Jaacks

Hello everyone, I am using a command action with pre-defined user_commands in the device dictionary for switching relays, as described here: https://master.lavasoftware.org/static/docs/v2/actions-command.html The return value does not seem to be evaluated, though. The test continues even if my user_command fails. I would assume that this causes an infrastructure failure, resulting in an incomplete job. Why is this not the case? Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Schlachthofstrasse 20 21079 Hamburg Direct: +49 40 791 899 - 183 Fax: +49 40 791899 - 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com WE MAKE IT YOURS! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun

4 years, 11 months

1
0
0 0

Unable to register IRC channel for #linaro-lava

by Nagendra Singamsetti

Hi team, i am trying to login IRC channel for #linaro-lava. https://webchat.freenode.net/#linaro-lava But , There is no register option for new user. It takes me to the group as Unregistered user. Please share the proper link to complete the registration for #linaro-lava. thanks Regards Nagendra S

4 years, 11 months

2
2
0 0

/etc/qemu-ifup: no bridge for guest interface found

by Nagendra Singamsetti

Hi team, I am new to lava-server. I have written and uploaded the job description for QEMU-arm64 to boot. But I can see in logs both kerenl Image-qemuarm64.bin and rootfs core-image-minimal-qemuarm64.ext4 files are downloaded in /var/lib/lava/dispatcher/tmp/* directory. But i am getting following error . auto-login-action: Wait for prompt ['Linux version [0-9]'] (timeout 00:02:00) *W: /etc/qemu-ifup: no bridge for guest interface foundqemu-system-aarch64: -kernel /var/lib/lava/dispatcher/tmp/27/deployimages-otsvre77/kernel/Image-qemuarm64.bin: Could not open 'format=raw,file=/var/lib/lava/dispatcher/tmp/27/deployimages-otsvre77/rootfs/core-image-minimal-qemuarm64.ext4': No such file or directoryConnection closed* *Attaching .yaml file for job discription.* Please let me know if i miss anything. Note : LAVA-SERVER version:version: 2019.01-5 QEMU boot command:sudo qemu-system-aarch64 -kernel Image-qemuarm64.bin -netdev tap,id=net0,ifname=tap1,script=no,downscript=no -device virtio-net-device,netdev=net0 -machine virt -cpu cortex-a57 -drive id=disk0,file=core-image-minimal-qemuarm64.ext4,if=none,format=raw -device virtio-blk-device,drive=disk0 -no-reboot -nographic -m 512 --append "root=/dev/vda rw console=ttyAMA0,38400 mem=512M highres=off ip=192.168.7.4: :192.168.7.3:255.255.255.0 rootfstype=ext4 console=ttyS0" Tested and working fine on my debian machine(with out lava server) thanks Regards Nagendra S

4 years, 12 months

2
4
0 0

Support for lauterbach-trace32 debugger

by Nagendra Singamsetti

Hi Team, Hi Team, Thanks for giving kind support. We are booting *ARM-cortexM targets* using lauterbach - trace32 debugger. http://www.embeddedindia.com/lauterbach-gmbh.html I would like to know *lauterbach** -trace32 debugger support* in lava If support is available, Please share me the supported Device-type jinja file or share me the reference file. Please let me know anything required from my side. I am looking forward your kind support thanks Regards Nagendra S

4 years, 12 months

2
3
0 0

Default lava-slave went offline

by Nagendra Singamsetti

Hi Team, Today i have started working with remote worker. But In Lava-server Admin page i have noticed that default lava-worker went office where as remote worker operations are working fine as expected. 1. Is this expected behavior ?? On command prompt i can see lava-slave status as Online [image: default_worker_onserver_command_line showing_online.png] Where as On webpage it is showing offline: [image: default_worker_onserver_webpage_status_offline.png] The devices connected to default worker also showing offline. 2. Can we rename hostname for remote worker?? Thanks !! Regards Nagendra S

5 years

1
0
0 0

Question about Docker feature for Android testing.

by Larry Shen

Hi, guys, I have a question after listen Docker feature for Android testing<https://linarotechdays.sched.com/event/ZZFc/ltd20-103-improved-android-test…>, and the question is a little long. 1. I want to say sorry that I haven't ever tried it on android because currently not urgent for us to switch from lxc to docker. But my real question is related to this feature at least I think. 2. The whole story is: We have a device which use the "tftpboot(deploy) -> nfs(boot) -> shell(test)" mode to test, that's ok. But now we have a team which for their testcases, they need to define other logic which behavior totally different with current lava solution. There is legacy code on pc which we want to reuse, so the quicker way for us is to use docker device, in it we could do anything to control the device. What we tried is: - Deploy (to: docker) - Boot (method: docker) - Test It's ok, as you see we could use the connection from boot in test. But as you know, not all device type accepts docker actions. Then, I find the option after you give the presentation in linaro tech share, use docker test. 3. I tried the v2020.02 release, it's ok to use next with any device type in our job to do my things. - test: docker: image: ubuntu:18.04 Although some android related log printed like "- ANDROID_SERIAL='xxx'", but I can bear. 4. Things broken when you improve this feature in v2020.04, you add next in pipeline: WaitDeviceBoardID(self.get_board_id() Then, the pipeline will have to wait for a udev event, but in our case, we don't have, we control device with "remote telnet device", then job hang. 5. So, my question here is: "What's the roadmap of this docker test action"? a) Is it just for android scenario? b) Why we can't make it works for more common scenario? My opinion here is: with this docker test action, we even no longer need the old "docker deploy + docker boot"? c) For this docker test, most of docker operation was written fixed in docker test, if possible to add in some place which user could configure? Like, if I want to add "-t", I can't control that although you define the interface in "DockerRun" with "def tty(self):", and others like more docker bind mounts etc? 6. BTW, a side question related to android (As definitely someday we need to switch from lxc to docker, I use this chance to ask the question). What will happened if there is adbd restart or pdu reboot in "docker test"? You add "-device" for the usb bus (I'm not sure, just think it same way as lxc), but during adbd restart or pdu reboot, the usb bus will surely changes. I didn't see docker has such kinds of ability to renew the "-device". How would that happen? Sorry again, I haven't tired, just want to know the mechanism. 7. Anyway, currently what I care about is the roadmap of "docker test". If your final direction is to make the "docker test" more common, then we are OK currently "STICK ON 2020.02". If just for android & "WaitDeviceBoardID" had to be here without any control by user, then we will give up this solution & try to find another way to reuse the device in LAVA? Your direction matters our next step! 8. Finally, Any other suggestion for our scenario which I described in item 2? Regards, Larry

5 years

2
6
0 0

Question about uboot action retry and timeout?

by Larry Shen

Hi, I have a question related to uboot boot action's retry settings, our job is: - boot: failure_retry: 2 namespace: test_suite_1 connection-namespace: burning-uboot_1 method: u-boot commands: nfs auto_login: login_prompt: '(.*) login:' username: root prompts: - 'root@(.*):~#' timeout: minutes: 10 1. From the code: "UBootAction" extends from a RetryAction, while in its internal pipeline, there is action named "UBootRetry" which also extends from RetryAction. If we define a "retry", when exception happened in "RetryAction", it will first cause "UbootRetry" to retry, then "UBootAction" to retry again. Sounds confuse, I wonder for what reason we should had a nested retry here? 2. In fact the real issue here for us is next: Let's suppose we define failure_retry: 2, our situation is: 1) First boot timeout for some random block issue. 2) Then, it start Retrying: 4.4 uboot-retry (599 sec), but timeout again. 3) Then, it start Retrying: 4 uboot-action (599 sec), but timeout again. 4) Then, it start Retrying: 4.4 uboot-retry (599 sec), this time a lucky boot here, but before we are happy, it finish the last action "export-device-env" in uboot-retry. Then, looks like "UBootAction" timeout resume, then the lucky boot becomes useless although it's in fact successfully boot. The log is: start: 4.4.5 expect-shell-connection (timeout 00:07:23) [test_suite_1] Forcing a shell prompt, looking for ['root@(.*):~#'] root@imx8mnevk:~# expect-shell-connection: Wait for prompt ['root@(.*):~#'] (timeout 00:10:00) Waiting using forced prompt support. 299.9747439622879s timeout end: 4.4.5 expect-shell-connection (duration 00:00:00) [test_suite_1] start: 4.4.6 export-device-env (timeout 00:07:23) [test_suite_1] end: 4.4.6 export-device-env (duration 00:00:00) [test_suite_1] uboot-action timed out after 727 seconds end: 4.4 uboot-retry (duration 00:02:07) [test_suite_1] I'm not sure, but looks like: for second "uboot-action", there is two "uboot-retry" inside it because of "retry", which will make when "uboot-action" timeout resume, the time diff becomes less than 0, which directly raise exception? Is it a bug or I misunderstand it? duration = round(action_max_end_time - time.time()) if duration <= 0: signal.alarm(0) parent.timeout._timed_out(None, None) Any suggestion for this?

5 years

2
4
0 0

v2020.02: job definition for fastboot on the host via docker

by Stephen Lawrence

Hi, I have some questions about the new adb/fastboot support in LAVA 2020.02 described in the recent Tech Days LAVA presentation [1]. Main initial use cases are Android boot test, before moving on to running Android tests. Android is AOSP 9/10. [1] https://connect.linaro.org/resources/ltd20/ltd20-304/ Taking the boot test use case I was looking at Antonio's Example 1 from his presentation for fastboot deploy, boot and test. I found doc for test in the 2020.02 release note but nothing I could see for deploy or boot. In the LXC approach a typical job definition would have had target and host namespaces, with deploy and boot for the host space to create and boot the LXC container. Looking at Example 1 deploy from the presentation it looks like that is a largely a target fragment as it contains the image binary etc. A host deploy no longer being required as the Docker container is now created outside lava. Similarly the Example 1 boot looks like a target fragment and host boot fragment is not required as LAVA simply needs to run the specified Docker container. Then finally in Example 1 test the scope is the specified docker container so no namespace is required. Is my interpretation of the Example 1 slides correct? I tried some fragments that were causing fundamental errors that caused me to check here. Although as is often the case writing it out helps you get it straighter in your mind. If you have reasons to want to control fastboot for the flashing on the host is that possible? For example if you had the host side process scripted. Does the fastboot Docker OS need to be specified? I'm running 2020.02 on the Worker via lava-docker, with Docker support within the Worker container by sharing the host Docker socket to gain access to the Docker daemon. Regards Steve

5 years

2
1
0 0

job error with new fastboot in docker support

by Stephen Lawrence

Hi, I'm trialling the fastboot support in Docker introduced in LAVA v2020.02 and getting a fundamental job error about the deploy action of the job definition. I've checked against the examples from the recent Linaro Tech Day LAVA presentation but I can't see the source of the error. Could someone familiar with this new support please take a look at the job definition please? I'm thinking it must be something obvious. Error snippet: error_msg: None of the deployment strategies accepted your deployment parameters, reasons given: overlay: "to" parameter is not "overlay" docker: 'docker' not in the device configuration deploy methods download: "to" parameter is not "download" qemu-nfs: Full error: https://lava.genivi.org/scheduler/job/718 Job definition: https://lava.genivi.org/scheduler/job/718/definition One possible cause I can think of is that the LAVA Worker is running 2020.02, whilst the Server is running 2019.03+stretch. My assumption is that the job definition parsing occurs in the dispatcher but maybe that is not correct? The Server will be upgraded to match the Worker of course, but we took a two step approach whilst we first looked into Android support. Thanks for any help, Steve

5 years

2
4
0 0

Lava Server setup Issue

by Nagendra Singamsetti

Hi Team, I have recently installed lava server (master) in my Debian machine. My goal is to configure lava-server with *master- multiple workers* *Lava-server : Master* *[PFA] Debian configuration *: root@LavaServer:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster Now i am trying to setup multiple workers on other machine: Q : *Can i configure/Install the worker on different Operating System other than Debian ??* If [No], please describe the process or share the useful Doc thanks Regarding Nagendra S

5 years

3
3
0 0

Lava-Lab "Master" and "Dispatcher" servers configuration details

by koti koti

Hi, initially we have plan to connect 5 boards to my lava-master and lava-dispatchers. Please can some let me know servers configurations for this setup as mentioned below? a. Can you let me know the LAVA master server configuration ? ( Processor/DDR/memory etc... configurations details) b. Can you let me know the Dispatcher server configuration ? (Processor/DDR/memory etc...configuration details) . ( I guess Dispatcher server configuration may be less than Master server configuration) c. PDU (I guess initial we have plan to connect 5 targets) . (If possible please can you share me the Amazon link to orfer) d. Serial port hub . (I guess initial we have plan to connect 5 targets) . (If possible please can you share me the Amazon link to order) Regards, Koti

5 years

2
3
0 0

Audit log for user action?

by Larry Shen

Hi, there, If lava in some place possible to find who cancel a job? Or use lavacli or manual cancel a job? Or for which detail reason, the job was canceled? We are struggling to find why my job canceled sometimes, not sure someone not carefully do it or our external program by chance do it, especially when there are many people used the same master. Regards, Lary

5 years

2
5
0 0

Question about send delay for serial.

by Larry Shen

Sometimes for some device, when lava enter "/lava-55904/bin/lava-test-runner /lava-55904/0" It looks it will print: -sh: /lava-55904/bin/lava-test-runnera-55904/0: No such file or directory Looks some character miss. We increases the test_character_delay, looks useful, but I'm interested about the details, so for next which you mentioned in the code: What exactly "slow serial problems(iPXE)" mean, could you explain more about it or any reference materteral I can had a look? Then I could know: yes, it's exactly the same problem I have. >>> Extends pexpect.sendline so that it can support the delay argument which allows a delay between sending each character to get around slow serial problems (iPXE). pexpect sendline does exactly the same thing: calls send for the string then os.linesep.

5 years

2
2
0 0

About health check behavior?

by Larry Shen

Hi, there, Frequently, I found when a job becomes incomplete there will immediately a health check job on that device happen automatically to check the status of the device. But strange, some times I won't see that healthy check job. So, my question is: when I see that healthy check job, is it just by chance? Or it really designed that there will be a healthy check after incomplete job? Thanks. Regards, Larry

5 years

2
4
0 0

"Where're my failed tests, dudes?"

by Paul Sokolovsky

Hello, I hope that the mail subject set up an easy, cheerful background for this discussion ;-). This definitely goes into the "stupid questions" department. My plan was to collect "evidence"/feedback from my colleagues, then at the Connect BUD20, crash into LAVA/QA rooms and ask what I/we are doing wrong. As circumstances changed, but the "testing debt" only builds up, there's little choice but to try figure out these matters over a much narrower pipe. So, before proceeding to the question per se, let me theorize that the reasons why such questions come up at all, are sufficient differences in the intended LAVA usage patterns. In other words, how I'd like to use LAVA on the LITE team side may differ from how LAVA team intends it to be used, or how QA team uses (the biggest user would it be). The issue? How I'd intend to use it is IMHO one the most basic ways to use a test system. So, what's that usage? Well, I'm not much interested in "interactive" use (submit jobs manually from my machine). Our interest is in unattended automated CI, of which the testing system is the second half after the build system. So let me remind how our build system, Jenkins, works. Normally, it just builds binaries and uploads them to a publishing server. It's invisible to me in this phase, and my engineering work goes uninterrupted. But when a build fails, I get an email with details about a failure. And I'll continue to get them while it continues to fail. So, the only option I have is to go see the failure, investigate, and fix it. When I arrive at Jenkins, I can easily see which jobs failed and which not, then within each job, see which builds failed and which succeeded. That's very easy, because failed things are red, and successful things are green. So, we've now arrived at the main question of this email - Why I don't seem to be able to use LAVA in the same way? Why LAVA offers only "Incomplete" and "Complete" job statuses? "Incomplete" is understood - it's an infrastructure failure, such a job is definitely "failed". But "Complete" doesn't give me any useful information whether the job succeeded or failed. Because a "Complete" job may still have any number of tests failed. And that's exactly the "last mile" LAVA misses to go: for any test job, I want to see a cumulative number of test cases which failed, straight at the page like https://lite.validation.linaro.org/scheduler/alljobs . Then, I'd like to filter out jobs which has this number >0. Then I'd like to receive a notification only for "failed" jobs, "failed" defined as "status != Complete OR failed_testcases > 0". So, what am I missing and how to make LAVA work like the above? Thanks, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

5 years

4
15
0 0

2020.02: docker in docker support for fastboot docker deploy

by Stephen Lawrence

Hi, After the recent Linaro Tech Day LAVA presentation I have been looking into the new support in LAVA v2020.02 for deploying fastboot on the host to docker rather than lxc. I am running my lava worker in a docker image derived from the linaro lava docker images and so wanted to ask if the new feature supported docker in docker for the fastboot containerisation? Regards Steve

5 years

2
2
0 0

Submit Job

by Nikolina nici_nigel

Hello, I just started working with hardware, firmware and lava. You have a big documentation, but for me it's sometimes difficult to find something. I wanted to submit a job on just one device like my "bbb-03" and not on every beaglebone-black. Is there a device-tag to choose a device like "device_type: "? My next question is if there is also a worker tag for a job submit? For example I just want to run all "beaglebone-black" on my "worker2". Is there also a list of all job submissions tags with examples? I just found the one for the "actions" part. I'm sorry for disturbing and maybe the stupid question. But thank you for your answer in advance. I wish you a nice day

5 years

2
1
0 0

Delaying LAVA Release

by Remi Duraffort

Hello, As you know, we are trying to release a new version of LAVA every month. We are delaying this month release (2020.03) due to some issues and crashes that we found in the last days. Issues where found on staging.vlo, lavafed and meta-lava, proving that the CI is working. Where are currently working on fixing the issues and proving that LAVA is ready for release. The next release should be ready for the end of next week and would be called 2020.04. Rgds -- Rémi Duraffort LAVA Architect Linaro

5 years

1
0
0 0

Confusion between LAVA job definition "name" vs UI "description"

by Paul Sokolovsky

Hello, I recently went "on a spree" to submit a number of LAVA UI issues either accumulated in my mind or just caught on exhaustive search for a feature I miss. They are at https://git.lavasoftware.org/lava/lava/-/issues?scope=all&author_username=p… and I believe all of them worth fixing (and don't bring in concerns like backward compatibility). So, they're up for triaging by the maintainers and feedback from the community to confirm they're indeed such. (Then, I'd be able to help with addressing them, as much as I can). There're more issues, about which I'm less sure. So, instead of submitting such as bugs, let me ask for a feedback in the email, starting with this one: When you prepare a job definition YAML to submit to LAVA, in it you something like: job_name: 'zephyr-net-ping #823-2ac65a24' It may be not immediately obvious, but what you had as a "job name" in the YAML, ends up as a "description" when you visit job list in the LAVA UI (E.g. at https://validation.linaro.org/scheduler/alljobs). "Is it that much of a difference? Most people wouldn't even notice!" you may think, and I can only second that. I for one never paid attention to that for on-and-off, mostly very light usage of LAVA for some 10 years (i.e. I started yet with the previous version which might look different at all). And indeed, it won't make any difference until may want to start querying job results. And I would like to share a story of what that difference costed me. Here's a patch I submitted in June 2017: https://git.linaro.org/ci/job/configs.git/commit/lite-aeolus/lava-job-defin… with a commit message and inline comment of: "For some reason, LAVA doesn't allow to query by real job name, so we need to duplicate it as metadata." Here's another patch which I submitted based on the analysis I present here: https://review.linaro.org/c/ci/job/configs/+/34677 So, for almost 3 years I lived with a misconception that LAVA can't query by a job name. Call it an extreme case. Call me dumb. Say that there's autocompletion for field names and any person with some agility of mind would type different characters and would notice "description" as available field. Yeah, I did all that. But I'm with me from 3 years ago: for me, "job name" is "zephyr-net-ping #823-2ac65a24". "job description" would be something like "Ping Zephyr dumb_http_server sample with packets of different size and interval". To the best of my knowledge, there's no such a field in jobdef YAML to include such a description, and I definitely don't include it in my jobs, so never would I try to search anything in "description", for the lack thereof in my jobs. Unless I have too much time to apply random "genetic algorithms" to LAVA UI or just do exhaustive search thru it. Which I usually don't have time for (I'm not a test engineer, but a developer, with "test that code" always in backlog). Until recently, when testing debt has really become pressing, and I decided to face all "skeletons in closed" I had with LAVA ;-). So, even 3 years haven't passed until I "did my homework" on searching jobs by name. But my point would be that there should be no need for any "homework" regarding these matters, it all should just work right away without double-thinking and guesswork. And I would consider this a genuine bug. I'm less sure about fixing though. Because it's not a matter of just changing a few UI labels. It's more pervasive, as e.g. this URL shows: https://lite.validation.linaro.org/results/query/+custom?entity=testjob&con… And seeing that URL, one can actually conjecture how that "description" appeared in the UI: it's actually name of the database table. Which just bled into system public interface. Too bad, because another public interface uses "job name" for that field, and internal naming like db fields shouldn't prevail. Anyway, I'm not going to argue that DB should be migrated, and it won't help, as we definitely don't want to break existing queries, etc. So, the only way to fix that would be to alias existing "description" to clearer "name" (or "jobname", "job_name"), and perform mapping on DB access. I'm note sure if it's worth. Based on my experience, I'd go for it, and it doesn't sounds like rocker science. But only maintainers could imagine how kludgy it would be in the actual LAVA database and if it's worth it, taking into account other tasks and priorities. Thanks for reading the story (rant?). -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

5 years

3
3
0 0

Sample docker-compose.yml file to detect adb devices in "lava-dispatcher"

by koti koti

Hi, I am facing the issue while porting Host's "adb-devices" to lava-dispatcher docker. Please can some one provide the right steps to detect "adb-devices" in "lava-dispatcher" docker? Current steps: (still my lava-dispatcher fail to detect the Host's "adb-devices") ########### 1. Lauch the LAVA-lab using "docker-compose up" from the repo " https://github.com/danrue/lava-docker-compose.git" 2. add "/dev/bus/usb" , "/etc/udev/rules.d" and "privileged: True" to "lava-dispatcher" i.e " dispatcher: image: lavasoftware/lava-dispatcher:2019.12 container_name: lava_dispatcher privileged: True devices: - /dev/kvm # needed for QEMU - /dev/net/tun # needed for QEMU - /dev/bus/usb cap_add: - NET_ADMIN # needed for QEMU environment: - "DISPATCHER_HOSTNAME=--hostname=dispatcher" - "LOGGER_URL=tcp://server:5555" # url to send logs - "MASTER_URL=tcp://server:5556" # url of lava master volumes: - '/boot:/boot:ro' - '/lib/modules:/lib/modules:ro' - '/dev/bus/usb:/dev/bus/usb' - '/etc/udev/rules.d:/etc/udev/rules.d'" 3. Run the command #docker-compose up 4. Login to lava-dispatcher #docker exec -it <dispatcher-name" bash #apt-get update;apt-get install android-tools-adb android-tools-fastboot usbutils #adb devices Can some one let me know the steps to detect my host's "adb-devices" in lava-dispatcher's docker? Regards, Koti

5 years

3
8
0 0

test/tests execution on provision (booted) board with out "-boot" section. (Basically I am skipping deploy and boot sections)

by koti koti

Hi, I am able to boot and run the tests with Provisioned(booted) board using attached YAML i.e "working_yaml.yaml". But, I am facing the issue while running the tests on Provisioned (booted) board with out "-boot" section. (you can see my YAML file as mentioned below which I have used now) Please can some one help me for the same? 1. Basically I am facing the connection issue with out "-boot" section. 2. Why this dependency to connect terminal for boot section ? ( I am able to connect serial port when I use "-boot" section in yaml file) 3. Please can some one provide me right YAML to run my tests with out "-boot" section. ( to resolve serial connection issue with out "-boot" section) " device_type: beaglebone-black job_name: begalbone healthcheck timeouts: job: minutes: 30 action: minutes: 15 connection: minutes: 5 priority: medium visibility: public context: test_character_delay: 10 actions: #- boot: # timeout: # minutes: 15 # method: minimal ## reset: false ## auto_login: ## login_prompt: '.* login:' ## username: root # prompts: # - root@dragonboard-410c:~# - test: interactive: - name: reset prompts: ["#"] script: - name: reset command: reset " Regards, Koti

5 years

3
8
0 0

Re: [Lava-users] LAVA RESTful API feedback and plans (Stevan Radakovi?)

by Larry Shen

Interesting topic, one question: What will the new LAVA rest api look? a) or b) ? I wish it could b), then we could ease our master's pressure... a) Django-rest-framework alike, synchronous b) Tornado alike, asynchronous -----Original Message----- From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of lava-users-request(a)lists.lavasoftware.org Sent: Wednesday, March 11, 2020 8:00 PM To: lava-users(a)lists.lavasoftware.org Subject: [EXT] Lava-users Digest, Vol 19, Issue 2 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. LAVA RESTful API feedback and plans (Stevan Radakovi?) ---------------------------------------------------------------------- Message: 1 Date: Wed, 11 Mar 2020 09:17:00 +0100 From: Stevan Radakovi? <stevan.radakovic(a)linaro.org> To: "lava-users(a)lists.lavasoftware.org" <lava-users(a)lists.lavasoftware.org> Subject: [Lava-users] LAVA RESTful API feedback and plans Message-ID: <34b9c19d-b0eb-2d85-0c85-a4e536a1812e(a)linaro.org> Content-Type: text/plain; charset="utf-8"; Format="flowed" Hello community, With the LAVA release of 2020.02 we now have a REST API framework that we fell covers all the functionalities of the already existing XMLRPC API. Since the long-term plan is to drop the XMLRPC support, we now encourage everyone to use REST and we also would like to hear feedback about any additional features that you'd like to see as part of the REST API. Our plan is to slowly move lavacli <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.lava…> project to use REST API exclusively, after that we will schedule the deprecation of the XMLRPC API. Cheers, -- Stevan Radakovi? | LAVA Engineer Linaro.org <https://eur01.safelinks.protection.outlook.com/?url=www.linaro.org&data…> ? Open source software for ARM SoCs

5 years

3
4
0 0

How to change defalut "soft reboot" commands in LAVA

by koti koti

Hi, Right now I am trying to run tests on Provisioned(booted) board with out using physical Power switches . But, I am seeing below soft reboot lines while using the attached YAML file, " start: 1 minimal-boot (timeout 00:15:00) [common] start: 1.1 connect-device (timeout 00:15:00) [common] [common] connect-device Connecting to device using 'telnet ser2net 5001' end: 1.1 connect-device (duration 00:00:01) [common] start: 1.2 reset-device (timeout 00:14:59) [common] start: 1.2.1 send-reboot-commands (timeout 00:14:59) [common] No soft reboot command defined in the test job. Using defaults. reboot reboot reboot -n reboot -n reboot -nf reboot -nf " I want to change my soft reboot command as "reset" instead of "reboot"/"reboot -n"/"reboot -nf". Please can some one let me know as how can I change default soft reboot command to "reset" ? Regards, Koti

5 years

3
8
0 0

LAVA tests execution on already provisioned (boot) begalbone board

by koti koti

Hi, I have successfully booted the Beagelbone board from " https://github.com/danrue/lava.therub.org" . (corresponding ymal is https://github.com/danrue/lava.therub.org/blob/master/server-overlay/etc/la… ) But, now I am trying to run one more scenario (may be new scenario and not sure is it supported by LAVA lab?) i.e 1. Run the tests on already provisioned (boot) beagelbone board. (Basically I am skipping the booting mentioned and trying to run on the already provisioned/boot board) a) boot the target b) Connect Board to LAVA lab c) Just check the login prompt ("#") is available or not? c) Run the using below test definition file (Basically this test definition file runs "ls"/"ifconfig" commands in the already provisioned(boot) board). " device_type: beaglebone-black job_name: beaglebone-black healthcheck timeouts: job: minutes: 10 action: minutes: 5 priority: high visibility: public actions: - test: interactive: - name: ls test prompts: ["#"] echo: discard script: - name: ls command: ls successes: - message: "ls simple test successes" failures: - message: "TIMEOUT" exception: InfrastructureError error: "ls command failed" - name: ifconfig command: ifconfig - name: wait for the prompt command: " I have tried to run this. But, my test failed with the error ""Connection closed"" (Attached screenshot) Can some one let me know solution to fix this error? Regards, koti

5 years, 1 month

3
3
0 0

LAVA RESTful API feedback and plans

by Stevan Radaković

Hello community, With the LAVA release of 2020.02 we now have a REST API framework that we fell covers all the functionalities of the already existing XMLRPC API. Since the long-term plan is to drop the XMLRPC support, we now encourage everyone to use REST and we also would like to hear feedback about any additional features that you'd like to see as part of the REST API. Our plan is to slowly move lavacli <https://docs.lavasoftware.org/lavacli/> project to use REST API exclusively, after that we will schedule the deprecation of the XMLRPC API. Cheers, -- Stevan Radaković | LAVA Engineer Linaro.org <www.linaro.org> │ Open source software for ARM SoCs

5 years, 1 month

1
0
0 0

Reboot inside test

by Ilya Fedusiv

Hi, lava team! First question: I'm working with fastboot device, is it possible after test part put device again to fastboot mode, run some fastboot command ( not to flash ), boot again, run test. job steps: 1. deploy lxc 2. boot lxc 3. test lxc 4. deploy fastboot ( put to fastboot ) 5. boot fastboot device 6. run test 7. reboot and put device to fastboot mode 8. run fastboot commands 9. continue run test. Can you give any advice how to do it? Better to able reboot device inside test. I tried to reboot device from test part, lava just stuck and wait when reboot action will end. But looks like it does not recognize end. Second question: In job have lxc namespace and device namespace, how to run command_action from host os, not lxc? Best regards, Ilya Feduisv

5 years, 1 month

2
1
0 0

Use user commands

by Ilya Fedusiv

Hi, Lava Team! Want to use user_commands as written here : https://validation.linaro.org/static/docs/v2/actions-command.html Device dictionary has : {% set user_commands = {'switch_mode' : {'do': './usr/local/scripts/switch_mode.sh'}} %} Job https://pastebin.com/hhWbC207 I have lxc and custom script to set device flash-mode. But have error error_msg: 'common' is a reserved namespace that should not be present with other namespaces To fix it I added namespace to command: - command: namespace: tlxc name: switch_to_qdl But error again in validate before submit Invalid definition: extra keys not allowed @ data['actions'][3]['command']['namespace'] I have fastboot and custom flash methods. pre_power_command in deploy I use for fastboot. Need to use somehow custom script to switch to another mode, that's why I decided to use -command action. Please help how to fix error with namespaces or suggest another solution. Best regards, Ilya Fedusiv

5 years, 1 month

2
3
0 0

Using "command" actions in multinode jobs

by Ryan Harkin

Hi LAVA folks, I'm trying to create a multinode job based on iperf.yaml: https://github.com/Linaro/test-definitions/blob/master/automated/linux/iper… (note, this iperf.sh test doesn't actually work as intended, but that's a problem I'm debugging). The full job definition is at the bottom of this email. Anyway, I'm adding my own deploy and boot sections, as per working single node jobs. However, my deploy uses "command" actions, like this: - command: role: - host - guest namespace: dfu-firmware name: set_boot_to_nand These give error messages like this: Invalid definition: extra keys not allowed @ data['actions'][1]['command']['role'] And if I remove the "role" settings, I get a different error: Valid definition with warnings: Every action of a multinode job should have roles So it seems like I'm in a loop. Any suggestions?? Thanks, Ryan. ------------------------------------------------------ JOB DEFINITION ------------------------------------------------------ job_name: lces2-iperf timeouts: job: minutes: 60 action: minutes: 3 connection: minutes: 5 priority: medium visibility: public metadata: iperf-version: v3 protocols: lava-multinode: roles: host: device_type: rzn1d count: 1 timeout: minutes: 30 guest: device_type: rzn1d count: 1 timeout: minutes: 30 actions: #################### # Deploy QSPI images #################### - deploy: role: - host - guest namespace: dfu-firmware to: tmpfs images: sf_fsbl: image_arg: --alt sf_fsbl --download {sf_fsbl} url: https://snapshots.linaro.org/openembedded/schneider/linaro-warrior-4.9/rzn1… sf_trustedfw: image_arg: --alt sf_trustedfw --download {sf_trustedfw} url: https://snapshots.linaro.org/openembedded/schneider/linaro-warrior-4.9/rzn1… sf_uboot0: image_arg: --alt sf_uboot0 --download {sf_uboot0} url: https://snapshots.linaro.org/openembedded/schneider/linaro-warrior-4.9/rzn1… sf_uboot1: image_arg: --alt sf_uboot1 --download {sf_uboot1} url: https://snapshots.linaro.org/openembedded/schneider/linaro-warrior-4.9/rzn1… - command: namespace: dfu-firmware role: - host - guest name: set_boot_to_nand - boot: namespace: dfu-firmware role: - host - guest method: dfu timeout: minutes: 10 - command: namespace: test role: - host - guest name: set_boot_to_qspi ############### # TFTP/NFS ############### - deploy: namespace: test-nfs role: - host - guest timeout: minutes: 5 to: tftp os: oe kernel: url: https://snapshots.linaro.org/openembedded/schneider/linaro-warrior-4.9/rzn1… type: zimage dtb: url: https://snapshots.linaro.org/openembedded/schneider/linaro-warrior-4.9/rzn1… nfsrootfs: url: https://snapshots.linaro.org/openembedded/schneider/linaro-warrior-4.9/rzn1… compression: bz2 - boot: namespace: test-nfs role: - host - guest connection-namespace: dfu-firmware timeout: minutes: 20 method: u-boot commands: - setenv autoload no - dhcp - dhcp - env print - setenv serverip {SERVER_IP} - tftp {KERNEL_ADDR} {KERNEL} - tftp {DTB_ADDR} {DTB} - setenv bootargs 'console=ttyS0,115200n8 root=/dev/nfs rw nfsroot={NFS_SERVER_IP}:{NFSROOTFS},tcp,hard,intr,vers=3 rootwait coherent_pool=2M ip=dhcp' - '{BOOTX}' auto_login: login_prompt: 'login:' username: root prompts: - 'root@snarc-soca9:' - 'root@rzn1-snarc:' - test: namespace: test-nfs role: - host timeout: minutes: 30 definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: run-iperf3-server description: "Run iperf3 in server mode" run: steps: - apt-get -y update - apt-get -y install iperf3 - if iperf3 -s -D; then lava-test-case run-iperf3-server --result 'pass'; else lava-test-raise 'Failed to run ipef3 server'; fi - lava-send server-ready ipaddr=$(lava-echo-ipv4 eth0) - lava-wait client-done - pkill iperf3 from: inline name: run-iperf3-server path: inline/run-iperf3-server.yaml - test: namespace: test-nfs role: - guest timeout: minutes: 30 definitions: - repository: https://git.linaro.org/people/chase.qi/test-definitions.git from: git path: automated/linux/iperf/iperf.yaml name: iperf3-test parameters: SERVER: lava-host-role # The MSG ID and KEY should be the same as the ones sent by lava-send above MSG_ID: server-ready MSG_KEY: ipaddr

5 years, 1 month

2
3
0 0

Re: [Lava-users] Unable to boot target via ipxe using nfs and tftp protocol via lava-docker container

by admirer mishra

Hi, I found the solution, we have to mount dispatcher.yaml file from lava-server in lava-master container as well beacuse lava-master is the one who communicate with DUT and run the job. regards admirer mishra

5 years, 1 month

1
0
0 0

Re: [Lava-users] Unable to boot target via ipxe using nfs and tftp protocol via lava-docker container

by admirer mishra

Hi Stevan, I am using latest lava-docker containers 2020.01 so using rest api I set the dispatcher ip and post it, which creates a dispatcher.yaml file with the content dispatcher_ip: '141.64.81.191' (not my ip) I checked it's there in the directory (/etc/lava-server/dispatcher.d/lava-dispatcher/dispatcher.yaml), but still no change in SERVER_IP or NFS_SERVER_IP (everything is same) while running the job, due to which not able to do tftp. I even tried with restarting the lava-server but still no change. Thanks for your time. regards, admirer mishra

5 years, 1 month

2
1
0 0

Unable to boot target via ipxe using nfs and tftp protocol via lava-docker container

by admirer mishra

Hi there, Yesterday, while going through the mail, I found about the docker-compose file provided by lava. The script is amazing it gives even more understanding of how actual lava-server and dispatcher work. I am a complete beginner just working on lava and docker from last 20 days. So, I am trying to boot a x86 device via ipxe using nfs and tftp protocol. In normal lava server running on host everything works fine because the host ip and target ip are on same local network so tftp and nfs works fine. But docker uses internal network and target is on local network so how to configure so that it works? I also used the docker compose file but the problem still persists. Is there any other configuration in the containers that I have to do make it work? Please help I am complete newbie in this field. Thanks for your time admirer mishra

5 years, 2 months

2
1
0 0

Lava Dispatcher Docker container tftp issue

by ROSHAN KUMAR

Hi, I am using the docker-compose file provided by lava community. I don't understand why there is a separate tftpd container and also how my device who is on host local network will communicate with it. Also same things I don't understand for nfs container. Please let me know Thanks and regards ROSHAN KUMAR

5 years, 2 months

3
3
0 0

Lava Server Docker container not working as Dispatcher

by ROSHAN KUMAR

Hi, I created a lava server docker container on amd64 machine using lavasoftware/lava-server docker image present on docker hub. But after running the container I didn't find any Dispatcher online except lava-logs. Did the current version of lava server docker container doesn't work as dispatcher similar to normal lava server. Please let me know. Thanks and regards ROSHAN KUMAR

5 years, 2 months

2
1
0 0

Mix device's type

by Ilya Fedusiv

Hi! I want to mix two flashing types for device : fastboot and custom ( run custom script ) I already did both types separately using deploy methods : fastboot and flasher How I can mix both types? And in web gui in device panel what does mean that error? Configuration Error: missing or invalid template. Jobs requesting this device type (mix-type) will not be able to start until a template is available on the master. Best regards, Ilya

5 years, 2 months

2
1
0 0

Dropping apache2 from lava-server container

by Remi Duraffort

Hello everyone, if you follow the latest developments, you might have seen that LAVA is now using whitenoise to allow gunicorn to serve static files. In the current releases (2020.01 and before), apache2 is forwarding dynamic requests to gunicorn and serving static files himself. In the next release, apache2 will forward all the requests to gunicorn that will serve both dynamic and static content. If you use the debian packages, apache2 will still be installed and configured automatically. We are proposing to drop the apache2 packages from the lava-server docker container. In fact, if you use the docker container, you have anyway to setup a reverse proxy to make the container visible to the outside world and to do the SSL termination. What do you think about this? Rgds -- Rémi Duraffort LAVA Architect Linaro

5 years, 2 months

2
3
0 0

Re: [Lava-users] Upgrade LAVA

by Remi Duraffort

The slaves/worker logs are in /var/log/lava-dispatcher/lava-slave.log Le mar. 11 févr. 2020 à 12:37, dhanu msys <dhanuskd.palnati(a)gmail.com> a écrit : > Hi Remi, > > After upgrading the LAVA Package , I have seen Worker Status show > "Offline". > > As per Earlier Experience , I have check the Lava-Logs and Lava-Master > Logs under /var/log/lava-server/lava-logs.log and > /var/log/lava-server/lava-master.log , it seems both are running fine > without any error. > > And also I have checked the Encryption in the both lava-master & lava-logs > under /etc/lava-server/lava-logs & /etc/lava-server/lava-master. PFA. > > Please check the attachment logs once and let me know if any changes need > to be done specific to the latest lava package. > > Thanks & Regards, > Dhanunjaya. P > > > On Wed, Feb 5, 2020 at 6:59 PM dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > >> Hi Remi, >> >> Thanks for sharing the Information. >> >> I can able to update the LAVA Package. >> >> Please find the latest packages list in below. >> >> doclava-aosp/stable 6.0.1+r55-1 all >> klavaro/stable 3.03-2 amd64 >> lava-common/unknown,now 2020.01+10+buster all [installed] >> lava-coordinator/unknown 2020.01+10+buster all [upgradable from: 0.1.7-1] >> lava-dev/unknown 2020.01+10+buster all [upgradable from: 2019.01-5] >> lava-dispatcher-host/unknown,now 2020.01+10+buster all >> [installed,automatic] >> lava-dispatcher/unknown,now 2020.01+10+buster all [installed] >> lava-lxc-mocker/unknown 2020.01+10+buster all >> lava-server-doc/unknown 2020.01+10+buster all [upgradable from: 2019.01-5] >> lava-server/unknown,now 2020.01+10+buster all [installed] >> lava-tool/stable,now 0.25-2 all [installed] >> lava/unknown,now 2020.01+10+buster all [installed] >> lavacli/unknown 0.9.7+buster all [upgradable from: 0.9.5-1] >> lavapdu-client/stable,now 0.0.5-1 all [installed] >> lavapdu-daemon/stable,now 0.0.5-1 all [installed] >> r-cran-lava/stable 1.6.4-1 all >> r-cran-lavaan/stable 0.6.3-1 all >> >> Thanks for immediate support. >> >> Regards, >> Dhanunjaya. P >> >> >> On Wed, Feb 5, 2020 at 3:55 PM Remi Duraffort <remi.duraffort(a)linaro.org> >> wrote: >> >>> Hello, >>> >>> add the apt lavasoftware depository. >>> >>> See >>> https://lava.readthedocs.io/en/latest/admin/basic-tutorials/instance/instal… >>> This will create a new source >>> "deb https://apt.lavasoftware.org/release buster main" >>> >>> >>> Rgds >>> >>> Le mer. 5 févr. 2020 à 05:59, dhanu msys <dhanuskd.palnati(a)gmail.com> a >>> écrit : >>> >>>> Hi Team, >>>> >>>> How to get the Latest Version changes in the LAVA Package for Single >>>> Instance? >>>> >>>> What is the Latest version released ? >>>> >>>> Please let me know the "How to Upgrade the Lava package without >>>> disturbing the existing test setup. >>>> >>>> Here I have attached the Lava packages list in my current setup to run >>>> the lava for reference. PFA. >>>> >>>> Thanks & Regards, >>>> Dhanunjaya. P >>>> _______________________________________________ >>>> Lava-users mailing list >>>> Lava-users(a)lists.lavasoftware.org >>>> https://lists.lavasoftware.org/mailman/listinfo/lava-users >>>> >>> >>> >>> -- >>> Rémi Duraffort >>> LAVA Architect >>> Linaro >>> >> -- Rémi Duraffort LAVA Architect Linaro

5 years, 2 months

2
1
0 0

Upgrade LAVA

by dhanu msys

Hi Team, How to get the Latest Version changes in the LAVA Package for Single Instance? What is the Latest version released ? Please let me know the "How to Upgrade the Lava package without disturbing the existing test setup. Here I have attached the Lava packages list in my current setup to run the lava for reference. PFA. Thanks & Regards, Dhanunjaya. P

5 years, 2 months

2
2
0 0

Re: [Lava-users] [EXT] Re: Test jobs to boot the target through JLink

by dhanu msys

Hi Andrei, Thanks for suggestion, I too had a same doubt before proceeding with the upgrade. I will try to setup the latest version in new system or i will take a backup of existing setup and run the test. Thanks & Regards, Dhanunjaya. P On Mon, Jan 27, 2020 at 2:24 PM Andrei Gansari <andrei.gansari(a)nxp.com> wrote: > Hello Dhanunjaya, > > > > These are the instructions on installing lava, you have to do something > similar to this in order to upgrade: > > https://docs.lavasoftware.org/lava/installing_on_debian.html > > > > I’m not sure if it will break or not your current setup, so be cautious > when upgrading, better backup if you have a live setup that is testing > other boards. > > > > I’m not a currently maintaining a LAVA server so I don’t have experience > updating from one version to another. > > Better you search the mailing list, ask on the mailing list or tryout on a > virtual machine. > > > > > > Andrei > > > > *From:* dhanu msys <dhanuskd.palnati(a)gmail.com> > *Sent:* Friday, January 24, 2020 12:44 PM > *To:* Andrei Gansari <andrei.gansari(a)nxp.com> > *Subject:* Re: [EXT] Re: [Lava-users] Test jobs to boot the target > through JLink > > > > *Caution: *EXT Email > > Hi Andrei, > > > > Can you please share the procedure to upgrade to the latest lava version. > > > > Thanks in advance. > > > > Regards, > > Dhanunjaya. P > > > > > > On Thu, Jan 23, 2020 at 7:33 PM Andrei Gansari <andrei.gansari(a)nxp.com> > wrote: > > From the screenshot it looks like you have a version of LAVA that does not > support jlink boot method. > > JLink was added in version 2019.10-1 > > > > Andrei > > > > *From:* dhanu msys <dhanuskd.palnati(a)gmail.com> > *Sent:* Thursday, January 23, 2020 3:13 PM > *To:* Andrei Gansari <andrei.gansari(a)nxp.com> > *Cc:* Kumar Gala <kumar.gala(a)linaro.org>; Andrei Gansari < > andrei.gansari(a)linaro.org>; lava-users <lava-users(a)lists.lavasoftware.org> > *Subject:* Re: [EXT] Re: [Lava-users] Test jobs to boot the target > through JLink > > > > *Caution: *EXT Email > > Hi Andrei, > > > > I run the test job based on the references shared by you. > > > > But , facing the error , while running the test job. > > > > Here I have attached the device template & device configuration files > along with the error. > > > > Please find the attachments & please provide me the inputs. > > > > Thanks in Advance. > > > > Regards, > > Dhanunjaya. P > > > > > > On Tue, Jan 21, 2020 at 5:29 PM Andrei Gansari <andrei.gansari(a)nxp.com> > wrote: > > Hello Dhanunjaya. P, > > > > You need to create a yaml file in > lava/lava_dispatcher/tests/sample_jobs/fpga_a64-jlink.yaml … assuming you > have already created the device fpga_a64. > > > > You have an example of FRDM-K64F booting cmsis-dap here: > > > https://github.com/Linaro/lite-lava-docker-compose/blob/lite/example/lava.j… > <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> > > You need to replace “method: cmsis-dap” -> “method: jlink” > > > > I didn’t run a clean lava environment, so I maybe missing something. > > > > > > Andrei G. > > > > *From:* dhanu msys <dhanuskd.palnati(a)gmail.com> > *Sent:* Tuesday, January 21, 2020 12:31 PM > *To:* Andrei Gansari <andrei.gansari(a)nxp.com> > *Cc:* Kumar Gala <kumar.gala(a)linaro.org>; Andrei Gansari < > andrei.gansari(a)linaro.org>; lava-users <lava-users(a)lists.lavasoftware.org> > *Subject:* Re: [EXT] Re: [Lava-users] Test jobs to boot the target > through JLink > > > > *Caution: *EXT Email > > Hi Andrei, > > > > Based on the information shared earlier , i have tried to configure the > device type to make use of jlink based boot method test job , but i have > faced an issue "Configuration Error: missing or invalid template*.* Jobs > requesting this device type (fpga_a64) will not be able to start until a > template is available on the master." > > > > Can you please check once and share the updated Device-Type Template also. > > > > Thanks & Regards, > > Dhanunjaya. P > > > > > > On Tue, Jan 21, 2020 at 3:28 PM dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > > Hi Andrei , > > Hi Kumar, > > > > Can you please share some of the Test Job definition references to check > the Jlink-based test jobs configurations. > > > > Thanks & Regards, > > Dhanunjaya. P > > > > > > On Tue, Nov 26, 2019 at 2:36 PM Andrei Gansari <andrei.gansari(a)nxp.com> > wrote: > > I’ve tested lava+jlink on Cortex M with both onboard debugger and external > debugger, like the one you referenced. > > You should change the following if needed: > > > > address: > > *0x00000000* > > options: > > - '-device *MK64FN1M0xxx12'* > > - '-if SWD' > > - '-speed 4000' > > > > The interface SWD is supported, not JTAG, that can be easily changed if > you need to. > > > > Regards, > > Andrei > > > > *From:* Lava-users <lava-users-bounces(a)lists.lavasoftware.org> *On Behalf > Of *dhanu msys > *Sent:* Tuesday, November 26, 2019 7:49 AM > *To:* Kumar Gala <kumar.gala(a)linaro.org> > *Cc:* Andrei Gansari <andrei.gansari(a)linaro.org>; lava-users < > lava-users(a)lists.lavasoftware.org> > *Subject:* [EXT] Re: [Lava-users] Test jobs to boot the target through > JLink > > > > *Caution: *EXT Email > > Hi Kumar, > > > > Thanks for sharing the reference. > > > > It's better to have some references for the test jobs submission also. > > > > Currently we are in initial phase to make use of LAVA , so we wants to > check the feasibility to deploy through JLink based test jobs. > > > > Here I have provided the JLink Interface , which we are going to use for > the development. > > > > > https://www.thingbits.net/products/segger-j-link-base-jtag-swd-debugger?utm… > <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.thing…> > > > > > Regards, > > Dhanunjaya. P > > > > > > On Sat, Nov 23, 2019 at 9:37 PM Kumar Gala <kumar.gala(a)linaro.org> wrote: > > > > > On Nov 21, 2019, at 11:06 PM, dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > > > > Hi Team, > > > > Can you please share some reference test jobs to run the tests using > J-Link boot method. > > Here’s a reference to the board cfg side change for J-Link: > > > https://github.com/agansari/lite-lava/blob/35a5bcbc01780638e6fd5e126bdfe180… > <https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co…> > > Andrei, > > Did you have a test job example to go along with this? > > - k > >

5 years, 2 months

1
1
0 0

lava-run crash after submitting a job

by Alexander Moore

Hello, Our internal LAVA setup has been hitting this crash intermittently (it reproduces about one out of every 30 job submissions). The below log snippet is from the 2019.07 LAVA docker images, but we updated to the 2019.12 images and the crash still occurs with the same error signature. lava-master | 2019-10-22 15:37:17,539 DEBUG |--> [523] scheduling lava-master | 2019-10-22 15:37:17,854 INFO [523] START => lava-dispatcher (CY8CKIT_062-01) lava-master | 2019-10-22 15:37:17,969 INFO [523] lava-dispatcher => START_OK lava-master | 2019-10-22 15:37:22,981 INFO [523] lava-dispatcher => END (lava-run crashed, mark job as INCOMPLETE) lava-master | 2019-10-22 15:37:23,038 ERROR [523] Unable to dump 'description.yaml' lava-master | 2019-10-22 15:37:23,038 ERROR [523] Compressed data ended before the end-of-stream marker was reached lava-master | Traceback (most recent call last): lava-master | File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 337, in _handle_end lava-master | description = lzma.decompress(compressed_description) lava-master | File "/usr/lib/python3.5/lzma.py", line 340, in decompress lava-master | raise LZMAError("Compressed data ended before the " lava-master | _lzma.LZMAError: Compressed data ended before the end-of-stream marker was reached Please let me know if I can provide any other info to help debug. Thanks, Alex This message and any attachments may contain confidential information from Cypress or its subsidiaries. If it has been received in error, please advise the sender and immediately delete this message.

5 years, 2 months

2
9
0 0

Device node in LXC is not accessible in hacking session

by Tim Jaacks

Hey everyone, I have a problem where a physical hardware device on my worker passed through to an LXC container cannot be read from or written to when I am connected to the LXC in a hacking session via SSH. I have registered the device in my static_info: {% set static_info = [ {"board_id": "GO31472"}, ] %} LAVA starts the LXC and attaches the device to it correctly: start: 2.2 lxc-add-static (timeout 00:04:50) [remote] Adding /dev/ttyUSB16, /dev/serial/by-id/usb-GFL_M_504_G_GO31472-if00-port0, /dev/bus/usb/004/008, /dev/serial/by-path/pci-0000:00:1d.3-usb-0:1:1.0-port0 nice lxc-device -n lxc-remote-10577 add /dev/ttyUSB16 nice lxc-device -n lxc-remote-10577 add /dev/serial/by-id/usb-GFL_M_504_G_GO31472-if00-port0 nice lxc-device -n lxc-remote-10577 add /dev/bus/usb/004/008 nice lxc-device -n lxc-remote-10577 add /dev/serial/by-path/pci-0000:00:1d.3-usb-0:1:1.0-port0 end: 2.2 lxc-add-static (duration 00:00:00) [remote] When I connect to the LXC via SSH using a hacking session, the device is there, but I cannot access it: root@lxc-remote-10577:~# ls -la /dev/ttyUSB16 crw-r--r-- 1 root root 180, 0 Aug 27 11:26 /dev/ttyUSB16 root@lxc-remote-10577:~# cat /dev/ttyUSB16 cat: /dev/ttyUSB16: Operation not permitted However, when I attach to the LXC directly from the worker using "lxc-attach", I can access it: root@lxc-remote-10577:~# ls -la /dev/ttyUSB16 crw-r--r-- 1 root root 180, 0 Aug 27 11:26 /dev/ttyUSB16 root@lxc-remote-10577:~# cat /dev/ttyUSB16 ��^C root@lxc-remote-10577:/# Did anybody else encounter such a problem before? Any hints on what might be the difference between lxc-attach and the SSH connection? Mit freundlichen Grüßen / Best regards Tim Jaacks DEVELOPMENT ENGINEER Garz & Fricke GmbH Schlachthofstrasse 20 21079 Hamburg Direct: +49 40 791 899 - 183 Fax: +49 40 791899 - 39 tim.jaacks(a)garz-fricke.com www.garz-fricke.com WE MAKE IT YOURS! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun

5 years, 2 months

1
0
0 0

Test jobs to boot the target through JLink

by dhanu msys

Hi Team, Can you please share some reference test jobs to run the tests using J-Link boot method. Thanks & Regards, Dhanunjaya. P

5 years, 3 months

3
8
0 0

Creating a multinode job

by Ryan Harkin

Hi folks, I'm struggling to create a working multinode job and wondered if someone could help? Here's the sample job I've submitted to try to get a handle on how multinode works: https://validation.linaro.org/scheduler/job/1963418.1#L1745 The main problem happens when LAVA executes this command on the shell: /lava-1963419/bin/lava-test-runner /lava-1963419/1 But there is no "/lava-1963419/1" directory, so then it can't find lava-common-functions and fails like this because the path is relative to a path that doesn't exist: /lava-1963419/bin/lava-test-runner: line 18: /lava-1963419/1/../bin/lava-common-functions: No such file or directory When I run a similar definition on a single node, it uses zero for the lava sub-dir, not 1, and it works: https://validation.linaro.org/scheduler/job/1963236#L2065 I tried to work out what was running here, to see if I could debug the scripts to work out where the "1" comes from. I cloned the LAVA repo and I cannot see the script "environment", and the lava-test-runner sources lava-common-functions from line 16, not 18. So now I'm curious where LAVA gets its scripts from. Another minor point, I'm following the instructions on this link: https://docs.lavasoftware.org/lava/writing-multinode.html And there are some dead links in there, eg. https://docs.lavasoftware.org/lava/examples/test-jobs/first-multinode-job.y… https://docs.lavasoftware.org/lava/examples/test-jobs/second-multinode-job.… https://docs.lavasoftware.org/lava/examples/test-jobs/bbb-lxc-ssh-guest.yaml Thanks, Ryan.

5 years, 3 months

2
3
0 0

grub boot

by Hemanth K V

Hello Lava Users, Trying to boot a target in LAVA based on base-grub device type.The LAVA version installed is 2019.11. >From the GRUB command line when I manually enter following commands for network setting ,it is getting executed successfully. grub> insmod efinet grub> net_ls_cards efinet2 20:87:56:b6:74:cd efinet1 20:87:56:f1:cf:21 efinet0 20:87:56:f1:cf:22 grub> net_add_addr test efinet0 134.86.62.99 grub> net_ls_addr test 20:87:56:f1:cf:22 134.86.62.99 But when I am sending same thing via LAVA , *net_add_addr test efinet0 134.86.62.99* [H[J[1;1Hgrub> net_add_addr test efinet0 134.86.62.99 bootloader-commands: Wait for prompt ['grub>'] (timeout 00:09:38) [1;7Hn[1;8H[1;8He[1;9H[1;9Ht[1;10H[1;10H_[1;11H[1;11Ha[1;12H[1;12Hd[1;13H[1;13Hd[1;14H[1;14H_[1;15H[1;15Ha[1;16H[1;16Hd[1;17H[1;17Hd[1;18H[1;18Hr[1;19H[1;19H [1;20H[1;20Ht[1;21H[1;21He[1;22H[1;22Hs[1;23H[1;23Ht[1;24H[1;24H [1;25H[1;25H [1;26H *error: three arguments expected.* The above error will come when we don't pass 3 parameters to net_add_addr grub> net_add_addr test efinet0 error: three arguments expected. I am getting this error even though 3 arguments are getting passed. Attached is the screen shot of the Job execution log. Thanks, Hemanth.

5 years, 3 months

3
4
0 0

Re: [Lava-users] Job Failure-Infrastructure error for qemu arm64

by Remi Duraffort

Hello, I ran the same job on staging (debian buster) and it's working fine: https://staging.validation.linaro.org/scheduler/job/266192 Something wrong on your system. Difficult to know. Could you send the full logs. Rgds Le mar. 14 janv. 2020 à 07:35, dhanu msys <dhanuskd.palnati(a)gmail.com> a écrit : > Hi Remi, > > Can you please check the logs and let me know what was the changes i need > to make to run the LAVA QEMU arm based test jobs. > > Thanks & Regards, > Dhanunjaya. P > > > On Mon, Dec 23, 2019 at 5:47 PM dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > >> Hi Remi, >> >> Can you able to check the below mentioned the Log Files & Job related >> configurations along with the Job failure logs. >> >> Thanks & Regards, >> Dhanunjaya. P >> >> >> On Thu, Nov 28, 2019 at 6:01 PM dhanu msys <dhanuskd.palnati(a)gmail.com> >> wrote: >> >>> Hi Remi, >>> >>> Here I have attached the test job definition , test summary details & >>> qemu device configuration file along with device template for qemu arm64 >>> architecture. PFA. >>> >>> Regards, >>> Dhanunjaya. P >>> >>> >>> On Tue, Nov 26, 2019 at 5:19 PM dhanu msys <dhanuskd.palnati(a)gmail.com> >>> wrote: >>> >>>> Hi Remi, >>>> >>>> Here I have attached the Host Information. >>>> >>>> root@Dhanu:~# uname -a >>>> Linux Dhanu 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) >>>> x86_64 GNU/Linux >>>> >>>> root@Dhanu:~# lsb_release -a >>>> No LSB modules are available. >>>> Distributor ID: Debian >>>> Description: Debian GNU/Linux 10 (buster) >>>> Release: 10 >>>> Codename: buster >>>> >>>> root@Dhanu:~# df -h >>>> Filesystem Size Used Avail Use% Mounted on >>>> udev 1.9G 0 1.9G 0% /dev >>>> tmpfs 383M 18M 365M 5% /run >>>> /dev/sda1 289G 23G 252G 9% / >>>> tmpfs 1.9G 375M 1.6G 20% /dev/shm >>>> tmpfs 5.0M 4.0K 5.0M 1% /run/lock >>>> tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup >>>> tmpfs 383M 5.7M 377M 2% /run/user/1000 >>>> >>>> And also I have attached the CPU Info & MemInfo related information for >>>> your reference. >>>> >>>> Regards, >>>> Dhanunjaya. P >>>> >>>> >>>> On Tue, Nov 26, 2019 at 3:17 PM Remi Duraffort < >>>> remi.duraffort(a)linaro.org> wrote: >>>> >>>>> Hi, >>>>> >>>>> >>>>> >>>>>> https://staging.validation.linaro.org/scheduler/device/staging-qemu03 >>>>>> >>>>>> >>>>>> This should work, unless your system is way too old. what host are >>>>> you using? >>>>> >>>>> >>>>> Rgds >>>>> >>>>> -- >>>>> Rémi Duraffort >>>>> LAVA Architect >>>>> Linaro >>>>> >>>> -- Rémi Duraffort LAVA Architect Linaro

5 years, 3 months

2
4
0 0

Lava dispatcher compatible question.

by David

Hello, all, Recently I heard from somebody said, lava will drop stretch support from 2020.01 release, I didn't find related information, is it true? I also want to know if I remain on stretch, but still use 2019.12 release just for slave, but maybe later just upgrade master to for example 2020.06 release on buster. Will 2019.12 slave on stretch be compatible with 2020.06(Just a example version) master on buster? Will you promise it? Best Regards, David

5 years, 3 months

2
2
0 0

Lava dispatcher compatible question.

by David

Hello, all, Recently I heard from somebody said, lava will drop stretch support from 2020.01 release, I didn't find related information, is it true? I also want to know if I remain on stretch, but still use 2019.12 release just for slave, but maybe later just upgrade master to for example 2020.06 release on buster. Will 2019.12 slave on stretch be compatible with 2020.06(Just a example version) master on buster? Will you promise it? Best Regards, David

5 years, 3 months

1
0
0 0

lavacli cannot fetch big logs.

by Larry Shen

Hi, there, We have one job to do some stress test, the final log is about 270MB. We use `lavacli -i production jobs logs --raw 30686` to fetch the log, it gives me next: ``` $ time lavacli -i production jobs logs --raw 30686 /usr/lib/python3/dist-packages/lavacli/__init__.py:101: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details. config = yaml.load(f_conf.read()) Unable to call 'jobs.logs': <ProtocolError for http://larry.shen:xxx@xxx.nxp.com/RPC2: 500 ('Connection broken: IncompleteRead(0 bytes read)', IncompleteRead(0 bytes read))> real 0m39.006s user 0m0.989s sys 0m0.191s ``` I check the gunicorn log, it give me: [2020-01-08 08:11:12 +0000] [188] [CRITICAL] WORKER TIMEOUT (pid:11506) Any suggestion?

5 years, 3 months

3
8
0 0

docker dispatcher qemu mount problem since 2019.11

by Dan Rue

I tried updating my lava-docker-compose repo to the latest but hit a problem mounting the overlay filesystem in qemu as of 2019.11 (2019.10 and earlier works, 2019.11 and later do not). To reproduce, clone https://github.com/danrue/lava-docker-compose/ and run "make"; observe the qemu health-check time out. The health check job can be found at https://github.com/danrue/lava-docker-compose/blob/master/server-overlay/et… The problem seems to occur when it tries to mount the overlay filesystem for the test job. I see in the release notes that the containers moved to buster in 2019.11 - related? Raw output below. Thanks, Dan / # mkdir /lava-2 mkdir /lava-2 mount /dev/disk/by-uuid/16786250-75bd-4703-9d57-7cfa618c725e -t ext2 /lava-2 / # mount /dev/disk/by-uuid/16786250-75bd-4703-9d57-7cfa618c725e -t ext2 /lava-2 mount /dev/disk/by-uuid/16786250-75bd-4703-9d57-7cfa618c725e -t ext2 /lava-2 mount: mounting /dev/disk/by-uuid/16786250-75bd-4703-9d57-7cfa618c725e on /lava-2 failed: No such file or directory ls -la /lava-2/bin/lava-test-runner / # ls -la /lava-2/bin/lava-test-runner ls -la /lava-2/bin/lava-test-runner ls: /lava-2/bin/lava-test-runner: No such file or directory Using /lava-2 export SHELL=/bin/sh / # export SHELL=/bin/sh export SHELL=/bin/sh . /lava-2/environment / # . /lava-2/environment . /lava-2/environment /bin/sh: .: can't open '/lava-2/environment' /lava-2/bin/lava-test-runner /lava-2/0 / # /lava-2/bin/lava-test-runner /lava-2/0 Test shell timeout: 10s (minimum of the action and connection timeout) /lava-2/bin/lava-test-runner /lava-2/0 /bin/sh: /lava-2/bin/lava-test-runner: not found

5 years, 3 months

3
2
0 0

Implement new deployment method

by Ilya Fedusiv

Hi! I'm trying to implement new method to lava. As a reference I took fastboot. Now I can job with my new implemented method. I want to work with lxc container as with fastboot. But same job as for fastboot with lxc, doesn't create lxc container and miss step with image validation. Only start methods which are described in /lava_dispatcher/actions/deploy/qdl.py What I miss? Kind regards, Ilya

5 years, 3 months

2
1
0 0

Job Failure-Infrastructure error for qemu arm64

by dhanu msys

Hi Team, I have tried to run the QEMU related jobs for arm64 with the below configurations , throwing an error. Can you please let me know the what was the Infrastructure missing on this job. Thanks & Regards, Dhanunjaya. P

5 years, 4 months

2
6
0 0

ACME Cape support in LAVA

by Milosz Wasilewski

Hi, I'm trying to change the way LAVA searches for and passes USB devices to LXC containers. Current code depends on arbitrary variables present in the static_info dictionary that is part of the device dictionary. This seems to be a problem for some users [1]. So the proposal was made to get rid of the arbitrary variables entirely and use udev variables (starting with ID_). The change was pretty simple to implement but when I started changing the docs I realized there were other classes of devices supported with static_info. Docs list ACME Cape that can be connected over LAN [2]. I'm not aware of any users of this code but I don't want to break the feature if there is anyone using it. So if you're users of LAVA who connect ACME Cape using static_info please reply to this thread. If I don't hear any replies I will remove this support. [1] https://git.lavasoftware.org/lava/lava/issues/335 [2] https://github.com/ARM-software/lisa/wiki/Energy-Meters-Requirements#user-c… Best Regards, milosz

5 years, 4 months

2
2
0 0

Re: [Lava-users] Deploy RTOS Based Application Image

by Remi Duraffort

What kind of command do you run to flash over usb? Le jeu. 28 nov. 2019 à 13:26, dhanu msys <dhanuskd.palnati(a)gmail.com> a écrit : > Hi Remi, > > We were flashing through USB otg cable. > > USB deploy method supported by lava right? > > Regards, > Dhanunjaya > > On Thu, Nov 28, 2019, 17:52 Remi Duraffort <remi.duraffort(a)linaro.org> > wrote: > >> Hello, >> >> you should give more information if you want to have a proper answer. >> >> How do you flash the board? is it fully automatic? >> Is this method already supported by LAVA? >> >> >> Rgds >> >> Le jeu. 28 nov. 2019 à 07:48, dhanu msys <dhanuskd.palnati(a)gmail.com> a >> écrit : >> >>> Hi Team, >>> >>> How can i deploy RTOS based Application Image on target. >>> >>> Notes : >>> Target HW : STM32F429I-DISC1. >>> RTOS : Open source RTOS >>> Application Image (RTOS + Application specific code). >>> >>> We are able to flash the Developed Application Firmware (.out/.bin) >>> through IAR IDE via USB, so we are in plan to make use of LAVA and run test >>> applications automatically. >>> >>> So , Can you please provide some references to deploy this test >>> scenarios in LAVA. >>> >>> Thanks & Regards, >>> Dhanunjaya. P >>> _______________________________________________ >>> Lava-users mailing list >>> Lava-users(a)lists.lavasoftware.org >>> https://lists.lavasoftware.org/mailman/listinfo/lava-users >> >> >> >> -- >> Rémi Duraffort >> LAVA Architect >> Linaro >> > -- Rémi Duraffort LAVA Architect Linaro

5 years, 4 months

3
6
0 0

RFC: when to drop stretch support?

by Remi Duraffort

Hello everyone, Summary: We would like to drop the support for stretch in the (near) future. Details: Currently lava-server and lava-dispatcher are supported on both debian stretch and debian buster. Since LAVA 2019.11, the lava-server and lava-dispatcher docker images are based on debian buster and not stretch. Unittest are still running on stretch, buster and bullseye but integration tests (lavafed and meta-lava mainly) are using the docker container so they run only on buster. Dropping the support for stretch will: * simplify testing * allow to use more recent version of python and django * remove some issues with old dependencies in stretch But before dropping the support we need to ensure that users/admins had some time to migrate to buster or to docker-based installations. In an ideal world, I would drop the support for stretch on the 1st of January 2020. But please answer to this mail so we can device of the right date all together. Thanks -- Rémi Duraffort LAVA Architect Linaro

5 years, 4 months

3
8
0 0

Value for connections lava-test-shell timeouts.

by Larry Shen

Hi, there, We can set lava-test-shell timeouts in test job like next: timeouts: connections: lava-test-shell: minutes: 1 My question is: what's the suitable value for this? Any performance consideration for this value, or in one word, what if I set it as small as possible?

5 years, 4 months

1
0
0 0

Interactive test action unreliable behavior

by Philippe Mazet

Hi All, I am experimenting with the interactive test action, but cannot get it to work reliably. I tried to replicate what is documented here: https://docs.lavasoftware.org/lava/interactive.html#writing-tests-interacti… I also took as example a job mentioned previously on this mailing list: https://validation.linaro.org/scheduler/job/1925569/definition But If I come down to the simplest uboot test job (yaml + log attached), I still see false verdicts. I first set 2 variables in uboot. Then I print them, and verify if the output contains the expected string. Only the first case behaves as expected: "fail-expected-1". All following tests go wrong: Test case "fail-expected-2" fails, but for a wrong reason: "Matched a prompt (was expecting a success): '=> '" And remaining test cases also show a wrong verdict because of this. Including the last 2 TCs which are supposed to pass, but are marked as failed. I also tested in Linux and on a different platform, and the behavior is the same. Am I missing something with the syntax? Or with serial console settings? Thanks a lot for your help, Philippe Mazet

5 years, 4 months

2
3
0 0

lxc creation fails with multiple containers

by Diego Russo

Hello, Sometimes LAVA slaves end up in a funky state where all jobs will be failing for the lxc-creation. This is an just a section of the pstree but actually the machine is not doing anything. No CPU/IO/memory usage at all. |-lxc-ubuntu,26488 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/mbl-rpi3-healthcheck-lxc-86216 --name=mbl-rpi3-healthcheck-lxc-86216 --rootfs=/var/lib/lxc/mbl-rpi3-healthcheck-lxc-86216/rootfs --release xenial ... | `-lxc-ubuntu,26495 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/mbl-rpi3-healthcheck-lxc-86216 --name=mbl-rpi3-healthcheck-lxc-86216 --rootfs=/var/lib/lxc/mbl-rpi3-healthcheck-lxc-86216/rootfs --release xenial ... | `-flock,26496 -x 9 |-lxc-ubuntu,29367 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/cellular-wifi-lxc-85573 --name=cellular-wifi-lxc-85573 --rootfs=/var/lib/lxc/cellular-wifi-lxc-85573/rootfs --release xenial --packages ... | `-lxc-ubuntu,29374 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/cellular-wifi-lxc-85573 --name=cellular-wifi-lxc-85573 --rootfs=/var/lib/lxc/cellular-wifi-lxc-85573/rootfs --release xenial --packages ... | `-rsync,29590 -Ha /var/cache/lxc/xenial/rootfs-amd64/ /var/lib/lxc/cellular-wifi-lxc-85573/rootfs/ | `-rsync,29593 -Ha /var/cache/lxc/xenial/rootfs-amd64/ /var/lib/lxc/cellular-wifi-lxc-85573/rootfs/ | `-rsync,29594 -Ha /var/cache/lxc/xenial/rootfs-amd64/ /var/lib/lxc/cellular-wifi-lxc-85573/rootfs/ |-lxc-ubuntu,30173 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/multi_component-image-update-pelion-lxc-85584 --name=multi_component-image-update-pelion-lxc-85584... | `-lxc-ubuntu,30186 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/multi_component-image-update-pelion-lxc-85584 --name=multi_component-image-update-pelion-lxc-85584... | `-flock,30187 -x 9 |-lxc-ubuntu,30226 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/helloworld-update-lxc-85537 --name=helloworld-update-lxc-85537 --rootfs=/var/lib/lxc/helloworld-update-lxc-85537/rootfs --release xenial --packages ... | `-lxc-ubuntu,30233 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/helloworld-update-lxc-85537 --name=helloworld-update-lxc-85537 --rootfs=/var/lib/lxc/helloworld-update-lxc-85537/rootfs --release xenial --packages ... | `-flock,30234 -x 9 |-lxc-ubuntu,30800 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/rootfs-image-update-mbl-cli-lxc-85588 --name=rootfs-image-update-mbl-cli-lxc-85588 --rootfs=/var/lib/lxc/rootfs-image-update-mbl-cli-lxc-85588/rootfs ... | `-lxc-ubuntu,30807 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/rootfs-image-update-mbl-cli-lxc-85588 --name=rootfs-image-update-mbl-cli-lxc-85588 --rootfs=/var/lib/lxc/rootfs-image-update-mbl-cli-lxc-85588/rootfs ... | `-flock,30808 -x 9 |-lxc-ubuntu,30837 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/mbl-cli-basic-commands-lxc-85540 --name=mbl-cli-basic-commands-lxc-85540 --rootfs=/var/lib/lxc/mbl-cli-basic-commands-lxc-85540/rootfs --release xenial ... | `-lxc-ubuntu,30844 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/mbl-cli-basic-commands-lxc-85540 --name=mbl-cli-basic-commands-lxc-85540 --rootfs=/var/lib/lxc/mbl-cli-basic-commands-lxc-85540/rootfs --release xenial ... | `-flock,30845 -x 9 |-lxc-ubuntu,31697 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/wifi-access-lxc-85591 --name=wifi-access-lxc-85591 --rootfs=/var/lib/lxc/wifi-access-lxc-85591/rootfs --release xenial --packages systemd,systemd-sysv | `-lxc-ubuntu,31704 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/wifi-access-lxc-85591 --name=wifi-access-lxc-85591 --rootfs=/var/lib/lxc/wifi-access-lxc-85591/rootfs --release xenial --packages systemd,systemd-sysv | `-flock,31705 -x 9 |-lxc-ubuntu,31800 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/multi_component-image-update-mbl-cli-lxc-85542 --name=multi_component-image-update-mbl-cli-lxc-85542... | `-lxc-ubuntu,31807 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/multi_component-image-update-mbl-cli-lxc-85542 --name=multi_component-image-update-mbl-cli-lxc-85542... | `-flock,31808 -x 9 I have tens and tens of this processes. LAVA jobs have failed but lxc processes are still there. It seems to be some sort of deadlock in the lxc world. I'm on Debian stretch 9.8. It recently started with no apparent reason. Regards -- 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/docs/mbed-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.

5 years, 4 months

3
2
0 0

Deploy RTOS Based Application Image

by dhanu msys

Hi Team, How can i deploy RTOS based Application Image on target. Notes : Target HW : STM32F429I-DISC1. RTOS : Open source RTOS Application Image (RTOS + Application specific code). We are able to flash the Developed Application Firmware (.out/.bin) through IAR IDE via USB, so we are in plan to make use of LAVA and run test applications automatically. So , Can you please provide some references to deploy this test scenarios in LAVA. Thanks & Regards, Dhanunjaya. P

5 years, 4 months

2
1
0 0

Re: [Lava-users] None of the deployment strategies accepted your deployment parameters

by dhanu msys

Hi Milosz, Thanks for providing the document references. I will try my level best. Thanks & Regards, Dhanunjaya On Tue, Nov 12, 2019, 20:36 Milosz Wasilewski <milosz.wasilewski(a)linaro.org> wrote: > I'll defer you to the docs: > - boot commands: > https://master.lavasoftware.org/static/docs/v2/actions-boot.html#index-9 > - device type: > > https://master.lavasoftware.org/static/docs/v2/devicetypes.html#device-types > - u-boot bootloader: > https://master.lavasoftware.org/static/docs/v2/actions-boot.html#index-35 > > I didn't test tftp booting with this board, so I can't help. It should > work as this is supported in device type: > > https://git.lavasoftware.org/lava/lava/blob/master/etc/dispatcher-config/de… > > Good luck. > > milosz > > On Tue, 12 Nov 2019 at 13:59, dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > > > > Hi Milosz, > > > > I was running tftp on my localhost & kept those uImage & dtb files in > the "tftpboot" repository. PFA. > > > > > > Thanks & Regards, > > Dhanunjaya. P > > > > > > On Tue, Nov 12, 2019 at 7:23 PM dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > >> > >> Hi Milosz, > >> > >> Yes , I have booted my board manually using the tftp , here i have > attached those uImage & dtb images. PFA. > >> Once the device bootsup , through command prompt , i will set the > following commands. > >> > >> setenv ipaddr 192.168.1.201 > >> setenv gatewayip 192.168.1.200 > >> setenv serverip 192.168.1.200 > >> setenv netmask 255.255.255.0 > >> tftpboot 0xc2000000 uImage > >> tftpboot 0xc4000000 stm32mp157c-ev1.dtb > >> setenv bootargs 'root=/dev/mmcblk0p6 rootwait rw > console=ttySTM0,115200'bootm 0xc2000000 - 0xc4000000 > >> > >> Its basically ARM architecture based and bootloader "u-boot". > >> > >> Can you please suggest how i can deploy the tftp files through LAVA > test job ,what will be the url i need pass in the job definition ? > >> > >> Thanks & Regards, > >> Dhanunjaya. P > >> > >> > >> On Tue, Nov 12, 2019 at 7:07 PM Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> wrote: > >>> > >>> Hmm, > >>> Do you know how tftp boot works? Loading 100M tarball into memory > >>> doesn't seem like a good idea. Which bootloader is running on your > >>> board? > >>> > >>> milosz > >>> > >>> On Tue, 12 Nov 2019 at 13:32, dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > >>> > > >>> > Hi Milosz, > >>> > > >>> > As per earlier email , I am trying to boot the STM32mp157c-dk2 with > the tftp deploy method , but getting failed to have proper device > configuration. > >>> > > >>> > Here I have attached the device configuration , device template & > Job definition files. PFA. > >>> > > >>> > Please let me know how to get resolve the issue. > >>> > > >>> > Regards, > >>> > Dhanunjaya. P > >>> > > >>> > > >>> > On Tue, Nov 12, 2019 at 2:45 PM Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> wrote: > >>> >> > >>> >> On Tue, 12 Nov 2019 at 08:14, dhanu msys < > dhanuskd.palnati(a)gmail.com> wrote: > >>> >> > > >>> >> > Hi Milosz, > >>> >> > > >>> >> > Currently eth008 was unavailable, Is there any possibility to > make use of Raspberry pi 4 as PDU to run power control commands on > STM32mp157c-dk2 ? > >>> >> > >>> >> Sure. Anything that can drive a relay will work. You will need to > >>> >> create a script that LAVA can call. Eth008 is a good choice for a > >>> >> bigger LAB where you need a lot of relays (these boards have > >>> >> configurable MAC addresses). If you need just one, than pick any > relay > >>> >> you can get on ebay and that will do the trick. > >>> >> > >>> >> milosz > >>> >> > >>> >> > > >>> >> > Thanks in advance. > >>> >> > > >>> >> > Regards, > >>> >> > Dhanunjaya. P > >>> >> > > >>> >> > > >>> >> > On Mon, Nov 11, 2019 at 5:36 PM dhanu msys < > dhanuskd.palnati(a)gmail.com> wrote: > >>> >> >> > >>> >> >> Hi Milosz, > >>> >> >> > >>> >> >> Thanks for the reply. > >>> >> >> > >>> >> >> I will try to get the eth008 if possible , otherwise i will try > to make use of TFTP or u-boot methods to run the test job on > STM32mp157c-dk2. > >>> >> >> > >>> >> >> Thanks & Regards, > >>> >> >> Dhanunjaya. P > >>> >> >> > >>> >> >> > >>> >> >> On Mon, Nov 11, 2019 at 4:57 PM Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> wrote: > >>> >> >>> > >>> >> >>> On Mon, 11 Nov 2019 at 11:07, dhanu msys < > dhanuskd.palnati(a)gmail.com> wrote: > >>> >> >>> > > >>> >> >>> > Hi Milosz, > >>> >> >>> > > >>> >> >>> > Really Thanks for sharing the Information. > >>> >> >>> > > >>> >> >>> > I have basic question, we can't able to run any test job for > the STM32 without external hardware(PDU) ? > >>> >> >>> > > >>> >> >>> > Can you please share the device configuration , which helps > to run the test jobs without "ethernet controlled relay" for the STM32. > >>> >> >>> > >>> >> >>> > https://git.linaro.org/lava/lava-lab.git/tree/shared/lab-scripts/eth008_con… > >>> >> >>> > >>> >> >>> > > >>> >> >>> > As I requested earlier , is there any possibility to run the > STM32 specific jobs with any other deployment methods(tmpfs , tftp..etc). > >>> >> >>> > >>> >> >>> Our boards use EFI for booting and I never tried tftp with > that. You > >>> >> >>> might need grub EFI application for that. Alternatively you > might use > >>> >> >>> u-boot. I didn't try that either. > >>> >> >>> > >>> >> >>> milosz > >>> >> >>> > >>> >> >>> > > >>> >> >>> > Thanks & Regards, > >>> >> >>> > Dhanunjaya. P > >>> >> >>> > > >>> >> >>> > > >>> >> >>> > On Mon, Nov 11, 2019 at 4:19 PM Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> wrote: > >>> >> >>> >> > >>> >> >>> >> Well, LAVA will try to switch the device into DFU mode for > deployment > >>> >> >>> >> step. These lines in the device dict do it: > >>> >> >>> >> '/usr/local/lab-scripts/eth008_control -a 172.27.19.27 -r 1 > -s on', > >>> >> >>> >> '/usr/local/lab-scripts/eth008_control -a 172.27.19.27 -r 2 > -s on', > >>> >> >>> >> Then it will power on the board: > >>> >> >>> >> '/usr/local/lab-scripts/snmp_pdu_control --hostname lngpdu01 > --command > >>> >> >>> >> on --port 3 --delay 20', > >>> >> >>> >> After that it will try to flash it using the > STM32_Programmer_CLI: > >>> >> >>> >> '/usr/local/bin/STM32_Programmer_CLI -c port=usb1 -w > {LAYOUT} -q', > >>> >> >>> >> Lastly it will power the board down and flip the dip > switches back: > >>> >> >>> >> '/usr/local/lab-scripts/snmp_pdu_control --hostname lngpdu01 > --command > >>> >> >>> >> off --port 3', > >>> >> >>> >> '/usr/local/lab-scripts/eth008_control -a 172.27.19.27 -r 1 > -s off', > >>> >> >>> >> '/usr/local/lab-scripts/eth008_control -a 172.27.19.27 -r 2 > -s off', > >>> >> >>> >> > >>> >> >>> >> So if you don't have HW moded board, this device dict won't > work for > >>> >> >>> >> you. Sources for the scripts are here: > >>> >> >>> >> > https://git.linaro.org/lava/lava-lab.git/tree/shared/lab-scripts > >>> >> >>> >> We're using pretty expensive HW in the LAB: > >>> >> >>> >> - managed APC PDUs: > >>> >> >>> >> > https://www.apc.com/shop/uk/en/products/Rack-PDU-Switched-1U-16A-208-230V-8… > >>> >> >>> >> (I couldn't find the exact models we have, they're > discontinued) > >>> >> >>> >> - ETH008 relay board: > https://www.robot-electronics.co.uk/htm/eth008tech.htm > >>> >> >>> >> > >>> >> >>> >> milosz > >>> >> >>> >> > >>> >> >>> >> On Mon, 11 Nov 2019 at 10:42, dhanu msys < > dhanuskd.palnati(a)gmail.com> wrote: > >>> >> >>> >> > > >>> >> >>> >> > Hi Milosz, > >>> >> >>> >> > > >>> >> >>> >> > No. > >>> >> >>> >> > Through Manual Setup , we are able to switch between the > modes. > >>> >> >>> >> > > >>> >> >>> >> > Here I have attached the kernel & dtb image for your > reference. PFA. > >>> >> >>> >> > > >>> >> >>> >> > Dhanunjaya. P > >>> >> >>> >> > > >>> >> >>> >> > > >>> >> >>> >> > On Mon, Nov 11, 2019 at 3:40 PM Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> wrote: > >>> >> >>> >> >> > >>> >> >>> >> >> I think I forgot to ask key question when it comes to > this device: did > >>> >> >>> >> >> you do the HW mod to be able to switch between DFU and OS > boot modes > >>> >> >>> >> >> without manual step? > >>> >> >>> >> >> > >>> >> >>> >> >> milosz > >>> >> >>> >> >> > >>> >> >>> >> >> On Mon, 11 Nov 2019 at 10:01, dhanu msys < > dhanuskd.palnati(a)gmail.com> wrote: > >>> >> >>> >> >> > > >>> >> >>> >> >> > Hi Milosz, > >>> >> >>> >> >> > > >>> >> >>> >> >> > Thanks for reply. > >>> >> >>> >> >> > > >>> >> >>> >> >> > I am new to the LAVA usage. > >>> >> >>> >> >> > > >>> >> >>> >> >> > I have taken reference from the below link. > >>> >> >>> >> >> > > https://staging.validation.linaro.org/scheduler/device/staging-stm32mp157-0… > >>> >> >>> >> >> > > >>> >> >>> >> >> > Here I have attached the device_dictionary & device > configurations files, PFA. > >>> >> >>> >> >> > > >>> >> >>> >> >> > Note : I am not able to see the "lab-scripts" to have > power controlled commands in my local repository , is there any specific > package need to install in my localhost , can you please share the > lab-scripts to have pdu control and also please share the pdu device > details if required to connect with the hardware. > >>> >> >>> >> >> > > >>> >> >>> >> >> > Can you please share some references , which i can run > some jobs through any other deploy methods like "tmpfs , tftp " for > "STM32MP157C-DK2". > >>> >> >>> >> >> > > >>> >> >>> >> >> > Thanks & Regards, > >>> >> >>> >> >> > Dhanunjaya. P > >>> >> >>> >> >> > > >>> >> >>> >> >> > > >>> >> >>> >> >> > On Mon, Nov 11, 2019 at 2:59 PM Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> wrote: > >>> >> >>> >> >> >> > >>> >> >>> >> >> >> Could you share your device dictionary? You might be > missing > >>> >> >>> >> >> >> flasher_deploy_commands. > >>> >> >>> >> >> >> > >>> >> >>> >> >> >> Please check here for reference: > >>> >> >>> >> >> >> > https://ledge.validation.linaro.org/scheduler/device/lng-stm32mp157-01/devi… > >>> >> >>> >> >> >> > >>> >> >>> >> >> >> milosz > >>> >> >>> >> >> >> > >>> >> >>> >> >> >> On Thu, 7 Nov 2019 at 07:48, dhanu msys < > dhanuskd.palnati(a)gmail.com> wrote: > >>> >> >>> >> >> >> > > >>> >> >>> >> >> >> > Hi Team, > >>> >> >>> >> >> >> > > >>> >> >>> >> >> >> > I am trying to run the test_jobs on the specific > device type "stm32mp1157c-dk2" , but its throwing an error message to > deploy "flasher" method in the deployment parameters. > >>> >> >>> >> >> >> > > >>> >> >>> >> >> >> > Here I have attached the screenshots for reference. > PFA. > >>> >> >>> >> >> >> > > >>> >> >>> >> >> >> > Thanks & Regards, > >>> >> >>> >> >> >> > Dhanunjaya. P > >>> >> >>> >> >> >> > _______________________________________________ > >>> >> >>> >> >> >> > Lava-users mailing list > >>> >> >>> >> >> >> > Lava-users(a)lists.lavasoftware.org > >>> >> >>> >> >> >> > > https://lists.lavasoftware.org/mailman/listinfo/lava-users >

5 years, 4 months

2
7
0 0

Re: [Lava-users] lxc creation fails with multiple containers

by Diego Russo

An update: as soon as I kll the rsync processes, all the lxc and flock processes get terminated. Before the killing I did try to create a lxc container from the command line but it was stuck. It continued after killing the rsync processes. How can I avoid this situation? Cheers -----Original Message----- From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> on behalf of Diego Russo <Diego.Russo(a)arm.com> Date: Tuesday, 26 November 2019 at 11:17 To: "lava-users(a)lists.lavasoftware.org" <lava-users(a)lists.lavasoftware.org> Subject: [Lava-users] lxc creation fails with multiple containers Hello, Sometimes LAVA slaves end up in a funky state where all jobs will be failing for the lxc-creation. This is an just a section of the pstree but actually the machine is not doing anything. No CPU/IO/memory usage at all. |-lxc-ubuntu,26488 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/mbl-rpi3-healthcheck-lxc-86216 --name=mbl-rpi3-healthcheck-lxc-86216 --rootfs=/var/lib/lxc/mbl-rpi3-healthcheck-lxc-86216/rootfs --release xenial ... | `-lxc-ubuntu,26495 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/mbl-rpi3-healthcheck-lxc-86216 --name=mbl-rpi3-healthcheck-lxc-86216 --rootfs=/var/lib/lxc/mbl-rpi3-healthcheck-lxc-86216/rootfs --release xenial ... | `-flock,26496 -x 9 |-lxc-ubuntu,29367 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/cellular-wifi-lxc-85573 --name=cellular-wifi-lxc-85573 --rootfs=/var/lib/lxc/cellular-wifi-lxc-85573/rootfs --release xenial --packages ... | `-lxc-ubuntu,29374 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/cellular-wifi-lxc-85573 --name=cellular-wifi-lxc-85573 --rootfs=/var/lib/lxc/cellular-wifi-lxc-85573/rootfs --release xenial --packages ... | `-rsync,29590 -Ha /var/cache/lxc/xenial/rootfs-amd64/ /var/lib/lxc/cellular-wifi-lxc-85573/rootfs/ | `-rsync,29593 -Ha /var/cache/lxc/xenial/rootfs-amd64/ /var/lib/lxc/cellular-wifi-lxc-85573/rootfs/ | `-rsync,29594 -Ha /var/cache/lxc/xenial/rootfs-amd64/ /var/lib/lxc/cellular-wifi-lxc-85573/rootfs/ |-lxc-ubuntu,30173 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/multi_component-image-update-pelion-lxc-85584 --name=multi_component-image-update-pelion-lxc-85584... | `-lxc-ubuntu,30186 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/multi_component-image-update-pelion-lxc-85584 --name=multi_component-image-update-pelion-lxc-85584... | `-flock,30187 -x 9 |-lxc-ubuntu,30226 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/helloworld-update-lxc-85537 --name=helloworld-update-lxc-85537 --rootfs=/var/lib/lxc/helloworld-update-lxc-85537/rootfs --release xenial --packages ... | `-lxc-ubuntu,30233 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/helloworld-update-lxc-85537 --name=helloworld-update-lxc-85537 --rootfs=/var/lib/lxc/helloworld-update-lxc-85537/rootfs --release xenial --packages ... | `-flock,30234 -x 9 |-lxc-ubuntu,30800 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/rootfs-image-update-mbl-cli-lxc-85588 --name=rootfs-image-update-mbl-cli-lxc-85588 --rootfs=/var/lib/lxc/rootfs-image-update-mbl-cli-lxc-85588/rootfs ... | `-lxc-ubuntu,30807 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/rootfs-image-update-mbl-cli-lxc-85588 --name=rootfs-image-update-mbl-cli-lxc-85588 --rootfs=/var/lib/lxc/rootfs-image-update-mbl-cli-lxc-85588/rootfs ... | `-flock,30808 -x 9 |-lxc-ubuntu,30837 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/mbl-cli-basic-commands-lxc-85540 --name=mbl-cli-basic-commands-lxc-85540 --rootfs=/var/lib/lxc/mbl-cli-basic-commands-lxc-85540/rootfs --release xenial ... | `-lxc-ubuntu,30844 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/mbl-cli-basic-commands-lxc-85540 --name=mbl-cli-basic-commands-lxc-85540 --rootfs=/var/lib/lxc/mbl-cli-basic-commands-lxc-85540/rootfs --release xenial ... | `-flock,30845 -x 9 |-lxc-ubuntu,31697 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/wifi-access-lxc-85591 --name=wifi-access-lxc-85591 --rootfs=/var/lib/lxc/wifi-access-lxc-85591/rootfs --release xenial --packages systemd,systemd-sysv | `-lxc-ubuntu,31704 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/wifi-access-lxc-85591 --name=wifi-access-lxc-85591 --rootfs=/var/lib/lxc/wifi-access-lxc-85591/rootfs --release xenial --packages systemd,systemd-sysv | `-flock,31705 -x 9 |-lxc-ubuntu,31800 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/multi_component-image-update-mbl-cli-lxc-85542 --name=multi_component-image-update-mbl-cli-lxc-85542... | `-lxc-ubuntu,31807 /usr/share/lxc/templates/lxc-ubuntu --path=/var/lib/lxc/multi_component-image-update-mbl-cli-lxc-85542 --name=multi_component-image-update-mbl-cli-lxc-85542... | `-flock,31808 -x 9 I have tens and tens of this processes. LAVA jobs have failed but lxc processes are still there. It seems to be some sort of deadlock in the lxc world. I'm on Debian stretch 9.8. It recently started with no apparent reason. Regards -- 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/docs/mbed-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. _______________________________________________ Lava-users mailing list Lava-users(a)lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users 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.

5 years, 4 months

1
0
0 0

LAVA master

by 宿川

Hi all, We upgraded our LAVA master to 2019.11 (2019.11 + stretch) version , but when queried devices owned by current user , it listed all devices hooked to this master, can anybody help check it? Regards, Su Chuan

5 years, 5 months

2
3
0 0

LXC connection LTP Issue

by Ilya Fedusiv

Hi! Have some issues with recognition of ltp test end point. After receiving message of the ltp's execution finish, job is still running and waiting with line : Listened to connection for namespace 'tlxc' done until get timeout. Also sometimes job runs good without that stuck. All scripts to run ltp were taken from lava's repo, without any changes. Just edit skipfile Here is end of log with stuck ltp https://pastebin.com/1qJAbxTJ Here is end of log with successful ltp recognition. https://pastebin.com/BnFyq5dU Here is test part of the job. https://pastebin.com/m6vAWkZ9 Ilya

5 years, 5 months

3
9
0 0

LAVA Lab System Specifications

by dhanu msys

Hi Team, Now I have experienced by running some of test jobs on LAVA Setup , really lava-mailing-lists helps a lot to solve problems & providing suggestions at earliest. Now We are planning to have LAVA Lab Setup with minimum 30 to 40 devices connected to the PDU to run automation test jobs. So , at initial we wants to know the LAVA Server Specifications more in detail , like RAM etc.. to setup the LAVA Lab. Regards, Dhanunjaya. P

5 years, 5 months

2
2
0 0

LAVA Web Interface access in intranet

by dhanu msys

Hi Team, I am able to access the web interface(WEB GUI) through localhost. Is there any specific configuration required to access the web ui within the intranet. Here I have shared the server.conf & instance.conf ( /etc/lava-server/ )files, please let me know the configuration changes if required? Dhanunjaya. P

5 years, 5 months

2
4
0 0

Re: [Lava-users] [Automated-testing] ELC followup / Search for a testing framework for small distribution tests on device

by Milosz Wasilewski

On Tue, 12 Nov 2019 at 16:49, Westermann, Oliver <Oliver.Westermann(a)cognex.com> wrote: > > Hey everyone, > > I recently joined the ELC in Lyon and had a good chat with a few who may read this list. Only during the ELC I leaned about the automated testing summit and if I had not planned the next days already, I would probably have joined. During the interesting talks and some networking I also learned about this list, so I now have to ask a bunch of questions in the hope for answers ;-) > > We (as in the company I work for) moved to linux for our embedded devices quite some time ago, but our testing hasn't. We have a test system for our full product, but due to the nature of the product ("cameras with intelligence"), there is a lot of implied requirements on the state of the device, which makes testing expensive (in terms of device- and setuptime), which results in only one, but very thorough test loop a day. > > We're now trying to check our options to setup a smaller on-device test-stage before this setup. We would like to test features we would consider "distribution features": Network connectivity, IO features, updates and more. Most devs have their small scripts to do one thing or another, but we would prefer to distribute something that allows us to share all this and run it as part of the CI chain. > > So I've looked into some of the pages on the Automated_Testing page of the elinux wiki and dove into a few of the frameworks, but actually I'm even more confused by LAVA, fuego and all the other tools than before. We already have a build system, we already have a CI system controlling build system. So I'm writing to you in an attempt to get a feeling for whats there and where we can contribute, and I will try to list some of our goal and ideas so maybe someone can throw me some good links (and hopefully, we can > > What we would like: > We would like to run simple tests (execute eg python & bash script) and validate the outputs > We would like to bring devices into a certain state, eg by an upgrade (we use sth with swupdate beneath) As LAVA co-maintainer I'm obviously biased but I think this tool can do what you need. LAVA doesn't do any building it expects build artifacts to be available for download. It can deliver software to your device (aka deployment step) and drive your device to run some tests. If you could give some more details about the device (how to deploy software to it, how to connect to console, etc.) I can probably suggest next step with LAVA. milosz > > Since I assume a lot of you have a better overview about whats out there, what sounds like our needs and where you think we could contribute, let me know :-) > > Best regards and thanks to all of those who gave talks at OSS and ELC, it was a very cool (and overwhelming) time :-) > > - Olli > > > -- > _______________________________________________ > automated-testing mailing list > automated-testing(a)yoctoproject.org > https://lists.yoctoproject.org/listinfo/automated-testing

5 years, 5 months

2
1
0 0

Re: [Lava-users] dispatcher_config not parsed

by Remi Duraffort

Hello, I said "lava-master" and not "lava-server". Le mar. 19 nov. 2019 à 11:56, Klaas Schulze-Dieckhoff < K.Schulze-Dieckhoff(a)sonnen.de> a écrit : > Hello Remi, > > > > yes it is visible, the first command-line output I showed in the original > message was from inside the lava-server container. I also played around > with the ownership of the file since it is a problem for devices/* and > health-check/* files (they must be lavaserver:lavaserver). But this didn’t > help… > > > > Thanks > > Klaas > > > > *Von:* Remi Duraffort <remi.duraffort(a)linaro.org> > *Gesendet:* Dienstag, 19. November 2019 11:09 > *An:* Klaas Schulze-Dieckhoff <K.Schulze-Dieckhoff(a)sonnen.de> > *Cc:* lava-users(a)lists.lavasoftware.org > *Betreff:* Re: [Lava-users] dispatcher_config not parsed > > > > Hello, > > > > is the configuration file > (/etc/lava-server/dispatcher.d/<hostname>/dispatcher.yaml) visible from the > master container? > > > > In the docker-compose setup, each service is running in a specific > container so the configuration files should be set carefully. > > > > > > Rgds > > > > Le mar. 19 nov. 2019 à 09:25, Klaas Schulze-Dieckhoff < > K.Schulze-Dieckhoff(a)sonnen.de> a écrit : > > Hi all, > > > > I am running lava using docker-compose. Additional to the official > docker-compose.yaml I added and FTP and NFS container. For testing my setup > I am trying to test a beaglebone black. > > In order to load dtb and kernel uboot needs to know the IP of the FTP / > NFS server. I added the IP in the following two ways: > > > > server: > > root@1a010c2f736b:/# cat > /etc/lava-server/dispatcher.d/lava-dispatcher.yaml > > dispatcher_ip: <server ip addr> > > > > dispatcher: > > root@075e2deb4c34:/# cat /etc/lava-dispatcher/lava-slave > > [....] > > NFS_SERVER_IP="<server-ip-addr> " > > > > The hostname of the dispatcher is `lava-dispatcher`. But, when the > health-check is running it will always run `setenv serverip > <ip-of-docker-container>. > > I also tried various variants of setting the dispatcher configuration > (./dispatcher.d/<hostname>/dispatcher.yaml, > ./dispatcher.d/<hostname>/env.yaml). No matter what I do lava persists to > take the IP of the docker-container. > > > > According to ` server/management/commands/lava-master.py` line 465 at > least one of the variants should word, > > > > I would appreciate some hints how to fix this! > > > > Thanks > Klaas > > > > Geschäftsführer: Christoph Ostermann (CEO), Oliver Koch, Steffen > Schneider, Hermann Schweizer, Tim Ulbricht. > Amtsgericht Kempten/Allgäu, Registernummer: 10655, Steuernummer > 127/137/50792, USt.-IdNr. DE272208908 > > _______________________________________________ > Lava-users mailing list > Lava-users(a)lists.lavasoftware.org > https://lists.lavasoftware.org/mailman/listinfo/lava-users > > > > > -- > > Rémi Duraffort > > LAVA Architect > > Linaro > > Geschäftsführer: Christoph Ostermann (CEO), Oliver Koch, Steffen > Schneider, Hermann Schweizer, Tim Ulbricht. > Amtsgericht Kempten/Allgäu, Registernummer: 10655, Steuernummer > 127/137/50792, USt.-IdNr. DE272208908 > -- Rémi Duraffort LAVA Architect Linaro

5 years, 5 months

1
0
0 0

dispatcher_config not parsed

by Klaas Schulze-Dieckhoff

Hi all, I am running lava using docker-compose. Additional to the official docker-compose.yaml I added and FTP and NFS container. For testing my setup I am trying to test a beaglebone black. In order to load dtb and kernel uboot needs to know the IP of the FTP / NFS server. I added the IP in the following two ways: server: root@1a010c2f736b:/# cat /etc/lava-server/dispatcher.d/lava-dispatcher.yaml dispatcher_ip: <server ip addr> dispatcher: root@075e2deb4c34:/# cat /etc/lava-dispatcher/lava-slave [....] NFS_SERVER_IP="<server-ip-addr> " The hostname of the dispatcher is `lava-dispatcher`. But, when the health-check is running it will always run `setenv serverip <ip-of-docker-container>. I also tried various variants of setting the dispatcher configuration (./dispatcher.d/<hostname>/dispatcher.yaml, ./dispatcher.d/<hostname>/env.yaml). No matter what I do lava persists to take the IP of the docker-container. According to ` server/management/commands/lava-master.py` line 465 at least one of the variants should word, I would appreciate some hints how to fix this! Thanks Klaas Gesch?ftsf?hrer: Christoph Ostermann (CEO), Oliver Koch, Steffen Schneider, Hermann Schweizer, Tim Ulbricht. Amtsgericht Kempten/Allg?u, Registernummer: 10655, Steuernummer 127/137/50792, USt.-IdNr. DE272208908

5 years, 5 months

2
1
0 0

docker-compose: libguestfs failing

by Klaas Schulze-Dieckhoff

Hi all, I am trying to run a lava-lab with the official docker-compose.yml. When running a health-check on a qemu-device it fails because libguestfs can't find a kernel inside /boot. (There is already a discussion running on the libguestfs-mailing list). But I think the underlying problem is, that there is really no kernel inside /boot of my lava-dispatcher container: #:~/linaro_lava/docker-compose$ docker-compose exec lava-dispatcher bash root@8b5507bd355a:/# ls -al /boot total 4124 drwxr-xr-x 6 root root 129 Oct 1 10:35 . drwxr-xr-x 57 root root 4096 Nov 5 06:04 .. drwxr-xr-x 2 root root 3 Oct 1 10:34 androidboot drwxr-xr-x 2 root root 3 Apr 25 2018 efi drwxr-xr-x 2 root root 3 Oct 1 10:34 grub lrwxrwxrwx 1 root root 28 Oct 1 10:34 initrd.img-core -> initrd.img-core-0.7.43+ppa27 -rw-r--r-- 1 root root 4218483 Oct 1 10:34 initrd.img-core-0.7.43+ppa27 drwxr-xr-x 2 root root 3 Oct 1 10:34 uboot Since /boot is mounted into the docker-container inside docker-compose.yml I would expect it to have the same content the on my host, which is not the case: #:~/linaro_lava/docker-compose$ ls -al /boot total 68300 drwxr-xr-x 4 root root 4096 Oct 30 08:17 . drwxr-xr-x 24 root root 4096 Oct 30 08:14 .. -rw------- 1 root root 4064684 Oct 1 03:02 System.map-4.15.0-66-generic -rw-r--r-- 1 root root 217362 Oct 1 03:02 config-4.15.0-66-generic drwxr-xr-x 3 root root 4096 Jan 1 1970 efi drwxr-xr-x 5 root root 4096 Nov 4 15:26 grub -rw-r--r-- 1 root root 57266820 Oct 30 08:17 initrd.img-4.15.0-66-generic -rw------- 1 root root 8363672 Oct 1 03:05 vmlinuz-4.15.0-66-generic Why can these both directories be different? I would really appreciate if somebody can help me out here! Thanks Klaas Geschäftsführer: Christoph Ostermann (CEO), Oliver Koch, Steffen Schneider, Hermann Schweizer, Tim Ulbricht. Amtsgericht Kempten/Allgäu, Registernummer: 10655, Steuernummer 127/137/50792, USt.-IdNr. DE272208908

5 years, 5 months

2
1
0 0

RPi3 and uboot 2019.10

by Diego Russo

Hello, We are using RPi3 B/B+ in our infrastructure and the latest uboot changed his behaviour in case of error. In our case we have a kernel and DTB but we don’t have the ramdisk. Despite this, LAVA tries the tftp command for the RAMDISK but the 2 versions have different errors. With uboot 2019.07 this is what happens: tftp - {RAMDISK} U-Boot> tftp - {RAMDISK} bootloader-commands: Wait for prompt ['U-Boot>', 'Resetting CPU', 'Must RESET board to recover', 'TIMEOUT', 'Retry count exceeded', 'Retry time exceeded; starting again', 'ERROR: The remote end did not respond in time.', 'Bad Linux ARM64 Image magic!', 'Wrong Ramdisk Image Format', 'Ramdisk image is corrupt or invalid', 'ERROR: Failed to allocate', 'TFTP error: trying to overwrite reserved memory'] (timeout 00:04:08) tftp - {RAMDISK} lan78xx_eth Waiting for PHY auto negotiation to complete...... done Using lan78xx_eth device TFTP from server 192.168.130.111; our IP address is 192.168.130.138 Filename '{RAMDISK}'. Load address: 0x0 Loading: * TFTP error: 'File not found' (1) Not retrying... Uboot 2019.10 has a different behaviour and throws a different error: tftp - {RAMDISK} U-Boot> tftp - {RAMDISK} bootloader-commands: Wait for prompt ['U-Boot>', 'Resetting CPU', 'Must RESET board to recover', 'TIMEOUT', 'Retry count exceeded', 'Retry time exceeded; starting again', 'ERROR: The remote end did not respond in time.', 'Bad Linux ARM64 Image magic!', 'Wrong Ramdisk Image Format', 'Ramdisk image is corrupt or invalid', 'ERROR: Failed to allocate', 'TFTP error: trying to overwrite reserved memory'] (timeout 00:04:12) tftp - {RAMDISK} lan78xx_eth Waiting for PHY auto negotiation to complete...... done Using lan78xx_eth device TFTP from server 192.168.130.111; our IP address is 192.168.130.138 Filename '{RAMDISK}'. TFTP error: trying to overwrite reserved memory... matched a bootloader error message: 'TFTP error: trying to overwrite reserved memory' (11) At this point LAVA fails the job because it matches the error message. What's the best way to solve the issue. How can I tell LAVA not to deal with the RAMDISK at all? Thanks -- 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/docs/mbed-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.

5 years, 5 months

3
8
0 0

Flasher action and pre power command

by Ilya Fedusiv

Hello! I'm trying to flash via special tool, which is not implemented in lava. I did it successfully by editing device dictionary. Next want to use pre power command. That's why I use lxc. But how trigger protocol to use it? It doesnt work: - deploy: namespace: target timeout: minutes: 20 to: flasher images: flash_dir: url: file:///opt/image.zip os: oe protocols: lava-lxc: - action: flasher-deploy request: pre-power-command Ilya

5 years, 5 months

2
3
0 0

Re: [Lava-users] None of the deployment strategies accepted your deployment parameters

by dhanu msys

Hi Milosz, Thanks for the reply. I will try to get the eth008 if possible , otherwise i will try to make use of TFTP or u-boot methods to run the test job on STM32mp157c-dk2. Thanks & Regards, Dhanunjaya. P On Mon, Nov 11, 2019 at 4:57 PM Milosz Wasilewski < milosz.wasilewski(a)linaro.org> wrote: > On Mon, 11 Nov 2019 at 11:07, dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > > > > Hi Milosz, > > > > Really Thanks for sharing the Information. > > > > I have basic question, we can't able to run any test job for the STM32 > without external hardware(PDU) ? > > > > Can you please share the device configuration , which helps to run the > test jobs without "ethernet controlled relay" for the STM32. > > > https://git.linaro.org/lava/lava-lab.git/tree/shared/lab-scripts/eth008_con… > > > > > As I requested earlier , is there any possibility to run the STM32 > specific jobs with any other deployment methods(tmpfs , tftp..etc). > > Our boards use EFI for booting and I never tried tftp with that. You > might need grub EFI application for that. Alternatively you might use > u-boot. I didn't try that either. > > milosz > > > > > Thanks & Regards, > > Dhanunjaya. P > > > > > > On Mon, Nov 11, 2019 at 4:19 PM Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> wrote: > >> > >> Well, LAVA will try to switch the device into DFU mode for deployment > >> step. These lines in the device dict do it: > >> '/usr/local/lab-scripts/eth008_control -a 172.27.19.27 -r 1 -s on', > >> '/usr/local/lab-scripts/eth008_control -a 172.27.19.27 -r 2 -s on', > >> Then it will power on the board: > >> '/usr/local/lab-scripts/snmp_pdu_control --hostname lngpdu01 --command > >> on --port 3 --delay 20', > >> After that it will try to flash it using the STM32_Programmer_CLI: > >> '/usr/local/bin/STM32_Programmer_CLI -c port=usb1 -w {LAYOUT} -q', > >> Lastly it will power the board down and flip the dip switches back: > >> '/usr/local/lab-scripts/snmp_pdu_control --hostname lngpdu01 --command > >> off --port 3', > >> '/usr/local/lab-scripts/eth008_control -a 172.27.19.27 -r 1 -s off', > >> '/usr/local/lab-scripts/eth008_control -a 172.27.19.27 -r 2 -s off', > >> > >> So if you don't have HW moded board, this device dict won't work for > >> you. Sources for the scripts are here: > >> https://git.linaro.org/lava/lava-lab.git/tree/shared/lab-scripts > >> We're using pretty expensive HW in the LAB: > >> - managed APC PDUs: > >> > https://www.apc.com/shop/uk/en/products/Rack-PDU-Switched-1U-16A-208-230V-8… > >> (I couldn't find the exact models we have, they're discontinued) > >> - ETH008 relay board: > https://www.robot-electronics.co.uk/htm/eth008tech.htm > >> > >> milosz > >> > >> On Mon, 11 Nov 2019 at 10:42, dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > >> > > >> > Hi Milosz, > >> > > >> > No. > >> > Through Manual Setup , we are able to switch between the modes. > >> > > >> > Here I have attached the kernel & dtb image for your reference. PFA. > >> > > >> > Dhanunjaya. P > >> > > >> > > >> > On Mon, Nov 11, 2019 at 3:40 PM Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> wrote: > >> >> > >> >> I think I forgot to ask key question when it comes to this device: > did > >> >> you do the HW mod to be able to switch between DFU and OS boot modes > >> >> without manual step? > >> >> > >> >> milosz > >> >> > >> >> On Mon, 11 Nov 2019 at 10:01, dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > >> >> > > >> >> > Hi Milosz, > >> >> > > >> >> > Thanks for reply. > >> >> > > >> >> > I am new to the LAVA usage. > >> >> > > >> >> > I have taken reference from the below link. > >> >> > > https://staging.validation.linaro.org/scheduler/device/staging-stm32mp157-0… > >> >> > > >> >> > Here I have attached the device_dictionary & device configurations > files, PFA. > >> >> > > >> >> > Note : I am not able to see the "lab-scripts" to have power > controlled commands in my local repository , is there any specific package > need to install in my localhost , can you please share the lab-scripts to > have pdu control and also please share the pdu device details if required > to connect with the hardware. > >> >> > > >> >> > Can you please share some references , which i can run some jobs > through any other deploy methods like "tmpfs , tftp " for "STM32MP157C-DK2". > >> >> > > >> >> > Thanks & Regards, > >> >> > Dhanunjaya. P > >> >> > > >> >> > > >> >> > On Mon, Nov 11, 2019 at 2:59 PM Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> wrote: > >> >> >> > >> >> >> Could you share your device dictionary? You might be missing > >> >> >> flasher_deploy_commands. > >> >> >> > >> >> >> Please check here for reference: > >> >> >> > https://ledge.validation.linaro.org/scheduler/device/lng-stm32mp157-01/devi… > >> >> >> > >> >> >> milosz > >> >> >> > >> >> >> On Thu, 7 Nov 2019 at 07:48, dhanu msys < > dhanuskd.palnati(a)gmail.com> wrote: > >> >> >> > > >> >> >> > Hi Team, > >> >> >> > > >> >> >> > I am trying to run the test_jobs on the specific device type > "stm32mp1157c-dk2" , but its throwing an error message to deploy "flasher" > method in the deployment parameters. > >> >> >> > > >> >> >> > Here I have attached the screenshots for reference. PFA. > >> >> >> > > >> >> >> > Thanks & Regards, > >> >> >> > Dhanunjaya. P > >> >> >> > _______________________________________________ > >> >> >> > Lava-users mailing list > >> >> >> > Lava-users(a)lists.lavasoftware.org > >> >> >> > https://lists.lavasoftware.org/mailman/listinfo/lava-users >

5 years, 5 months

2
4
0 0

Fork option is disabled

by Suram Suram

Hi, I want to submit a change to device-type file and when I tried from the webGUI after logging in, the fork option is disabled. After clicking on the forks count number, the fork option appears to be enabled on that page. Clicked it to select namespace, when hovered the mouse over the namespace, it shows the following error "You have reached your project limit" Can some one help me on this please? Regards Suram

5 years, 5 months

2
1
0 0

None of the deployment strategies accepted your deployment parameters

by dhanu msys

Hi Team, I am trying to run the test_jobs on the specific device type "stm32mp1157c-dk2" , but its throwing an error message to deploy "flasher" method in the deployment parameters. Here I have attached the screenshots for reference. PFA. Thanks & Regards, Dhanunjaya. P

5 years, 5 months

2
3
0 0

Force prompt in lava boot issue.

by Larry Shen

Guys, We have a problem as next: [cid:image001.jpg@01D5958F.E65E7670] The story is we have kernel exception when device boot, then per next code: if index == cls.TRACE or index == cls.EXCEPTION: res = "fail" if action: action.logger.warning( "%s: %s" % (action.name, cls.MESSAGE_CHOICES[index][2]) ) # TRACE may need a newline to force a prompt connection.sendline(connection.check_char) It will send a "#" to device, but unfortunately, the exception time is too close the final login, then the "#" was sent to user login as next: Imx8qxpmek login: # Then when we send "root", it definitely cannot login, how to resolve? More, why lava send "#" to device when kernel have exception?

5 years, 5 months

2
1
0 0

Re: [Lava-users] 500 internal server error

by Remi Duraffort

Hello, could you give me the exact version? If you are admin, just ask debian to give you the package version. If you are a user, this is printed in the first line of every job logs. Rgds Le lun. 4 nov. 2019 à 07:58, dhanu msys <dhanuskd.palnati(a)gmail.com> a écrit : > Hi Remi, > > I was using LAVA Version V2, please correct me if i am quite wrong. > > Please let me know how to find out the lava version using command prompt. > > Thanks & Regards, > Dhanunjaya. P > > > On Thu, Oct 31, 2019 at 9:42 PM Remi Duraffort <remi.duraffort(a)linaro.org> > wrote: > >> Hello, >> >> which version are you using? >> >> >> Rgds >> >> Le jeu. 31 oct. 2019 à 13:19, dhanu msys <dhanuskd.palnati(a)gmail.com> a >> écrit : >> >>> Hi Team, >>> >>> While Running LAVA in localhost , facing the error while accessing the >>> UI related to Devices. >>> >>> Here I have attached the screenshot , please find the attachment. >>> >>> Please help me to solve this issue. >>> >>> Thanks & Regards, >>> Dhanunjaya. P >>> _______________________________________________ >>> Lava-users mailing list >>> Lava-users(a)lists.lavasoftware.org >>> https://lists.lavasoftware.org/mailman/listinfo/lava-users >> >> >> >> -- >> Rémi Duraffort >> LAVA Architect >> Linaro >> > -- Rémi Duraffort LAVA Architect Linaro

5 years, 5 months

2
4
0 0

Lava Test Jobs didn't scheduled

by dhanu msys

Hi Team, I have submitted some sample test jobs for qemu device type on my local lava setup. After successful submission of tests , I can't able to see the jobs running status , the state remains to "submitted". When i gone through the lava-master logs , Observed the warnings saying that can't able to schedule the jobs due to lava-logs is offline. Here I have attached the screenshots. Please find the attachments. Can you please let me know how to schedule the jobs on master by manual. Thanks & Regards, Dhanunjaya. P

5 years, 5 months

2
10
0 0

Issue with prompt matching with no output during boot

by Diego Russo

Hello, We upgrade from LAVA 2019.04 to 2019.10 and we have issues with the prompt matching when the device boots. We test 2 kinds of Linux images: * Development image * it outputs data into the serial (secure boot, uboot, kernel, systemd) * user: root, pass: empty * Production image * it doesn't output anything and *only presents the login prompt* * user: root, pass: it could be anything The workflow is the following: * spin up LXC container for recovery mode * boot the DUT waiting for the prompt. We don't need to login using the serial connection but we need to wait the prompt to understand that the board has successfully booted * run tests from the LXC container and using ssh to the DUT In LAVA 2019.04 everything was working as expected: ... start: 7.3 auto-login-action (timeout 00:05:57) [target] Using line separator: #'\n'# No login prompt set. Parsing kernel messages ['-+\\[ cut here \\]-+\\s+(.*\\s+-+\\[ end trace (\\w*) \\]-+)', '(Unhandled fault.*)\\r\\n', 'Kernel panic - (.*) end Kernel panic', 'Stack:\\s+(.*\\s+-+\\[ end trace (\\w*) \\]-+)', 'mbed-linux-os-(.*) login:', 'Login timed out', 'Login incorrect'] [auto-login-action] Waiting for messages, (timeout 00:05:57) Waiting using forced prompt support. 178.45381999015808s timeout Trying ::1... Connected to localhost. Escape character is '^]'. Mbed Linux OS mbl-warrior-dev-production_build64 mbed-linux-os-674 ttymxc5 Matched prompt #4: mbed-linux-os-(.*) login: ... While in 2019.10 the job is failing with the following: ... start: 7.3 auto-login-action (timeout 00:05:57) [target] auto-login-action: Wait for prompt ['Linux version [0-9]'] (timeout 00:06:00) Trying ::1... Connected to localhost. Escape character is '^]'. � Mbed Linux OS mbl-warrior-dev-production_build74 mbed-linux-os-1764 ttymxc5 ... Another thing we observed in LAVA 2019.10: using the dev images (hence with output data) it works without any problem. Here a snippet of our pipeline: .... - boot: namespace: recovery timeout: minutes: 5 method: recovery commands: recovery - deploy: timeout: minutes: 10 to: recovery namespace: recovery connection: lxc images: images to download..... os: debian - test: namespace: lxc connection: lxc timeout: minutes: 10 definitions: - from: inline name: flash-image path: inline/flash-image.yaml repository: metadata: format: Lava-Test Test Definition 1.0 name: flash-image description: "Flash image to board in recovery mode" os: - oe run: steps: - steps to recover the board - boot: namespace: recovery timeout: minutes: 5 method: recovery commands: exit - boot: namespace: target method: minimal failure_retry: 3 prompts: - "mbed-linux-os-(.*) login:" timeout: minutes: 6 .... Looking at the LAVA code we think the following commit changed the behaviour: https://git.lavasoftware.org/lava/lava/commit/6b5698a2d3ed23031e40aa1d86181… How are we supposed to change the pipeline to make it work again? Thanks -- 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/docs/mbed-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.

5 years, 5 months

2
2
0 0

Unexpected crash.

by cnspring2002

Hi, Sometimes, lava master will show next error, then seems zemomq crash, do you know what's the potential cause? 2019-08-20 09:14:39,576 DEBUG lava-worker-1 => PING(20) 2019-08-20 09:14:39,578 DEBUG lava-worker-2 => PING(20) 2019-08-20 09:14:39,580 DEBUG lava-worker-3 => PING(20) 2019-08-20 09:14:44,467 ERROR [CLOSE] Unknown exception raised, leaving! 2019-08-20 09:14:44,467 ERROR 'utf-8' codec can't decode byte 0xc0 in position 10: invalid start byte Traceback (most recent call last): File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 687, in handle self.main_loop(options) File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 731, in main_loop while self.controler_socket(): # Unqueue all pending messages File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 234, in controler_socket hostname = u(msg[0]) File "/usr/lib/python3/dist-packages/zmq/utils/strtypes.py", line 34, in cast_unicode return s.decode(encoding, errors) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc0 in position 10: invalid start byte 2019-08-20 09:14:44,467 INFO [CLOSE] Closing the controler socket and dropping messages

5 years, 5 months

2
3
0 0

About associated log lines in suite page.

by Larry Shen

All, I'm testing some feature about associated log lines in lava, job.yaml is as follows. Job.yaml: - test: connection: lxc definitions: - from: inline name: my_suite path: me.yml repository: metadata: format: Lava-Test Test Definition 1.0 name: smoke-case-run description: Run smoke case run: steps: - lava-test-case "Case001" --shell 'echo wow' - lava-test-case "Case002" --shell 'ls' namespace: lxcEnv timeout: minutes: 10 1. Then, let's see next picture of Case001: [cid:image002.jpg@01D59322.5F8C2990] it said startline=153, lastline=154, that's next: Line153 is "Received signal: <STARTTC> Case001", Line 154 is "Received signal: <ENDTC> Case001". You could see in fact the log "wow" not in the 2 lines. [cid:image008.jpg@01D59322.5F8C2990] 2. let's see next picture of Case002: [cid:image009.jpg@01D59322.5F8C2990] It said startline=160, lastline=163, that's next: [cid:image010.jpg@01D59322.5F8C2990] It's ok, that between Ln160 & Ln163 I got the output of `ls`. What happened for "Case001"? The startline & endline not correct. It seems if I directly do "echo", the info is wrong. while "execute command", the info is correct. Of course my case will not just do "echo", just I want to know if any risk for me to fetch the wrong START/LAST lines in other scenario? (I will use script to fetch it with xmlrpc).

5 years, 5 months

2
1
0 0

removing support for boot['type']

by Milosz Wasilewski

Hi, When test job uses boot action with method: u-boot there was an option to tell it which boot command to call in u-boot shell. This was done using 'type' parameter. Example from docs: - boot: method: u-boot commands: nfs type: bootz prompts: - 'root@debian:~#' This parameter was deprecated for more than a year. I just submitted a patch to remove this feature. If you're using it, please consider changing to setup where kernel image type is set using deploy section. Example: - deploy: timeout: minutes: 4 to: tftp os: oe kernel: url: 'https://example.com/zImage' type: 'zimage' dtb: url: 'https://example.com/dtb.dtb' nfsrootfs: url: 'https://example.com/rootfs.tar.xz' compression: xz Pull request: https://git.lavasoftware.org/mwasilew/lava/pipelines/5794 milosz

5 years, 5 months

2
1
0 0

about lava scheduler

by cnspring2002

Does lava has roadmap to separate resource management to some open source mechenisim, so it could share resource with other framework? Like spark/hadoop could use mesos/yarn to share resource.

5 years, 5 months

2
2
0 0

How to search maillist?

by cnspring2002

I see next: > If you are having problems, it may be helpful to check the mailing list archives first I could see https://lists.lavasoftware.org/pipermail/lava-users/, but how can I search?

5 years, 5 months

2
1
0 0

500 internal server error

by dhanu msys

Hi Team, While Running LAVA in localhost , facing the error while accessing the UI related to Devices. Here I have attached the screenshot , please find the attachment. Please help me to solve this issue. Thanks & Regards, Dhanunjaya. P

5 years, 5 months

2
1
0 0

Job Submission

by dhanu msys

Hi Team, I was trying to run the first Job with the qemu device type , continuously the job listing as submitted , not getting into the Running status to observe the behaviour. As a Initial step , How I need to run the Scheduler, what will the mac address need to update in the device configuration file while running jobs in the localhost. Regards, Dhanunjaya. P

5 years, 5 months

1
1
0 0

lxc:/// and lxc-file systems connect

by Ilya Fedusiv

Hi, everyone! I'm using fastboot from lxc to flash image to device. I have link to archive of my image. How better operate with it? In lxc test download archive, unzip it to lxc, and flash it ? I've tried this option. And use lxc:/// url type. But I cant find it, can you suggest how to do it? my job description : https://pastebin.com/LUmL6Qv3 and I see my downloads in lxc file system. I just removed other commands from job. I understand,that it is wrong. I found in glossary http://59.144.98.45/static/docs/v2/glossary.html#term-lava-lxc-home But I cant connect path from lxc-container, and lxc:/// Please, help. Ilya

5 years, 5 months

2
1
0 0

Device Dictionary Configuration

by dhanu msys

Hi Team, i tried to add Device & Jobs to the LAVA instance for the device type "qemu" , continuously getting the Configuration Error:missing or invalid template(jobs requesting this device type (qemu) will not be able to start until a template is available on the master). Can you please let me know how to add Device Dictionary to the LAVA instance. Thanks in advance. Regards, Dhanunjaya. P

5 years, 6 months

2
1
0 0

Cannot click to see job results if request is running.

by cnspring2002

Hi, with lava2019.09 will has next issue, seems ok in 2019.01:if request is running, click something like next:http://lava_ip/results/171It will show:500 Internal Server Errorlist index out of range Oops, something has gone wrong! But if the request finish, the link ok again.

5 years, 6 months

2
2
0 0

Run LTP from LAVA

by Ilya Fedusiv

Hello! I run ltp test on my device. And now ltp's output goes in one test log output. Is it possible to separate output of ltp testcases? To show fail or pass on each test? Ilya.

5 years, 6 months

2
1
0 0

VTS and CTS timeout in Lava because of the maximum timeout of 60 min

by George Nistor

Hi, I have a Lava job which runs VTS and CTS and Lava gives me time out because the maximum timeout I could set was 60 min. How do I set no-Timeout for my test? Is it possible? george

5 years, 6 months

2
1
0 0

Re: [Lava-users] Lavacli jobs list usage

by Remi Duraffort

Perfect then. Thanks Le mer. 23 oct. 2019 à 09:42, Philippe BEGNIC <philippe.begnic(a)st.com> a écrit : > Hello Remi, > > The "start" parameters allows me to slice the windows by packets of 100 > jobs. This is OK for my usage. > > Thanks for your support > > Philippe Begnic > On 10/22/19 5:32 PM, Remi Duraffort wrote: > > Hello, > > this is the lava server that limit the number of jobs that will be > returned. But the api allows to iterate by setting the "start" parameter. > See https://validation.linaro.org/api/help/#scheduler.jobs.list > > > Rgds > > Le mar. 22 oct. 2019 à 16:17, Philippe BEGNIC <philippe.begnic(a)st.com> a > écrit : > >> Hello everyone, >> >> I am using Lavacli to calculate basic statistics on the daily jobs >> executed with LAVA. (Nbr of complete//incomplete//canceled jobs). >> I also display the failure reason of the incomplete and canceled jobs by >> parsing the jobs logs. >> I can only do this operation for a limited number of jobs, because it >> seems that Lavacli has a restriction on the number of jobs to be treated. >> (100 jobs) >> >> Here the command lines I am using : >> > lavacli jobs list --health INCOMPLETE --limit 200 >> >> To count the number of computed jobs: >> > lavacli jobs list --health INCOMPLETE --limit 200 |wc -l >> > 101 >> >> So, I have requested 200 jobs, and Lavacli has treated only 100 jobs ( >> Note that our jobs database contains more than 200 jobs incomplete) >> >> Is it possible to remove or to increase the limitation on the number of >> jobs to be treated ? >> >> >> Best regards >> >> >> Philippe Begnic >> STMicroelectronics | MDG Group – MCD Division >> >> >> _______________________________________________ >> Lava-users mailing list >> Lava-users(a)lists.lavasoftware.org >> https://lists.lavasoftware.org/mailman/listinfo/lava-users > > > > -- > Rémi Duraffort > LAVA Architect > Linaro > > -- Rémi Duraffort LAVA Architect Linaro

5 years, 6 months

2
1
0 0

overlay-unpack timeout error

by Philippe BEGNIC

Hello everyone, I have got an error in a lava job during to overlay unpacking operations. This happen with jobs that flash the DUT before executing the tests. When the partitions are flashed on the DUT, I reboot the boards. After kernel has started, the kernel boot prompt is detected. Then the commands to downloads the tests overlay are launched. ( wget ... ) But in my case, these commands are not immediately executed, because the DUT is beeing resizing the root filesystem to fit available disk space on the SDCard. This operation take time ( depending on capacity and characteristics of the SDCard), and cause overlay-unpack<https://citools.st.com/results/testcase/2039053> to fail with a timeout error, because the command wget is not executed in the expected time ( 30 sec is the default time ). I have tried to add a time out settings in the transfer_overlay part of my jobs, but this has no effect. Is it possible to set specific "timeout trigger" for the "overlay-unpack" operation ? My Lava version: 2019.01+stretch Best regards Philippe Begnic STMicroelectronics

5 years, 6 months

3
6
0 0

Re: [Lava-users] Unexpected crash. (Remi Duraffort)

by cnspring2002

Hi, Remi, You said: > lava-master is receiving an invalid zmq message. I guess you are not using encryption? Are you fuzzing it? Sorry, I did not catch you. What does fuzzing it mean? I did not do anything special for LAVA. Meanwhile, what does "not using encryption" mean? Is this a LAVA master configure item or something else? I did not change anything related to this. And as I said, it could work ok for some a period, then I leave the whole environment there, no touch for anything. Then severial days later, it may encountered the issue. BTW, even such things happen, why no a exception handing in LAVA to ignore such issue? Currently it just close the zeromq connection. ------------------------------------------------------------------ Sender:lava-users-request <lava-users-request(a)lists.lavasoftware.org> Sent At:2019 Oct. 15 (Tue.) 00:25 Recipient:lava-users <lava-users(a)lists.lavasoftware.org> Subject:Lava-users Digest, Vol 14, Issue 10 Send Lava-users mailing list submissions to lava-users(a)lists.lavasoftware.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.lavasoftware.org/mailman/listinfo/lava-users 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: lava job without any flashing on a real device (George Nistor) 2. Re: Unexpected crash. (Remi Duraffort) 3. Re: repeat in lava not work (Diego Russo) ---------------------------------------------------------------------- Message: 1 Date: Mon, 14 Oct 2019 13:17:55 +0000 From: George Nistor <george.n(a)l4b-software.com> To: "lava-users(a)lists.lavasoftware.org" <lava-users(a)lists.lavasoftware.org> Subject: Re: [Lava-users] lava job without any flashing on a real device Message-ID: <VI1PR01MB38711749B69B27E8410ABB41F0900(a)VI1PR01MB3871.eurprd01.prod.exchangelabs.com> Content-Type: text/plain; charset="utf-8" Yes, In my case the only way I could make lava to see the fastboot device was via running pre-power-command, and I run a script (I customized device descriptor to run a this script as pre-power-command) which does: 1. Power Off Wait 5s 2.Power On Wait 30s 3. Login as root Wait 5s 4. echo reboot bootloader. # make it go in fastboot mode Immediately after this script runs, the udev rule is triggered and device id added (seen from Lava). Otherwise the reboot does not work for me. The line: nice lxc-attach -n lxc-hikey-test-186 -- fastboot -s xxxxxxx reboot gives timeout. Because the device is not seen. To make the job work without any flashing I removed the - deploy section which does flashing entirely For my case: I have added to boot this section protocols: lava-lxc: - action: fastboot-boot request: pre-power-command timeout: minutes: 5 george The full job I cannot post due to company policy with confidentiality on projects. -----Original Message----- From: Milosz Wasilewski <milosz.wasilewski(a)linaro.org> Sent: luni, 14 octombrie 2019 15:58 To: George Nistor <george.n(a)l4b-software.com> Subject: Re: lava job without any flashing on a real device Could you send the question to ML? I don't know why adb is not enough. Maybe LAVA waits for udev event? milosz On Mon, 14 Oct 2019 at 13:51, George Nistor <george.n(a)l4b-software.com> wrote: > > I have managed after all to do it with a job like this: > My problem was to be able to run pre-power-command before boot, to make lava to see the fastboot device - trigger that python script lxc-device-add. > > > -----Original Message----- > From: Milosz Wasilewski <milosz.wasilewski(a)linaro.org> > Sent: Monday, October 14, 2019 15:02 > To: George Nistor <george.n(a)l4b-software.com> > Subject: Re: lava job without any flashing on a real device > > There was a feature called 'dummy deploy' but I can't find it any more. Did you try simply removing 'deploy' action? This should do the trick but you will need transfer_overlay in your boot section. > > milosz > > On Mon, 14 Oct 2019 at 12:33, George Nistor <george.n(a)l4b-software.com> wrote: > > > > Hi Milosz, > > > > > > > > I have a small question: > > > > Is it possible to run a lava job without any deploy – flashing sequence on a real device? > > > > > > > > I attach the job I’m working on. > > > > > > > > george ------------------------------ Message: 2 Date: Mon, 14 Oct 2019 15:34:24 +0200 From: Remi Duraffort <remi.duraffort(a)linaro.org> To: cnspring2002 <cnspring2002(a)aliyun.com> Cc: lava-users <lava-users(a)lists.lavasoftware.org> Subject: Re: [Lava-users] Unexpected crash. Message-ID: <CANJfhHchH1UZOy=ScC5CUnPkZ55yi3QXrNPqqjk6wSJBFZbrzg(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello, lava-master is receiving an invalid zmq message. I guess you are not using encryption? Are you fuzzing it? Le lun. 14 oct. 2019 à 11:18, cnspring2002 <cnspring2002(a)aliyun.com> a écrit : > Hi, Sometimes, lava master will show next error, then seems zemomq crash, > do you know what's the potential cause? > > 2019-08-20 09:14:39,576 DEBUG lava-worker-1 => PING(20) > 2019-08-20 09:14:39,578 DEBUG lava-worker-2 => PING(20) > 2019-08-20 09:14:39,580 DEBUG lava-worker-3 => PING(20) > 2019-08-20 09:14:44,467 ERROR [CLOSE] Unknown exception raised, leaving! > > 2019-08-20 09:14:44,467 ERROR 'utf-8' codec can't decode byte 0xc0 in position 10: invalid start byte > Traceback (most recent call last): > > File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 687, in handle > self.main_loop(options) > > File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 731, in main_loop > while self.controler_socket(): # Unqueue all pending messages > > File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 234, in controler_socket > hostname = u(msg[0]) > > File "/usr/lib/python3/dist-packages/zmq/utils/strtypes.py", line 34, in cast_unicode > return s.decode(encoding, errors) > > UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc0 in position 10: invalid start byte > > 2019-08-20 09:14:44,467 INFO [CLOSE] Closing the controler socket and dropping messages > _______________________________________________ > Lava-users mailing list > Lava-users(a)lists.lavasoftware.org > https://lists.lavasoftware.org/mailman/listinfo/lava-users -- Rémi Duraffort LAVA Tech Lead Linaro

5 years, 6 months

2
1
0 0

VTS does not start because of the adb

by George Nistor

I am still having this problem inside the lxc container with 'adb start-server' failed. Should I define something special in the jinja2 device descriptor regarding adb or in the job to be able to use it? george -----Original Message----- From: Milosz Wasilewski <milosz.wasilewski(a)linaro.org> Sent: Wednesday, October 16, 2019 12:59 To: George Nistor <george.n(a)l4b-software.com> Cc: lava-users(a)lists.lavasoftware.org Subject: Re: [Lava-users] VTS does not start because of the adb George, I understand what the LAVA job is doing. I'm asking you to check whether there is _any_ adb server running on the host? If there is, the server you're running in a container will not be able to connect to the device. milosz On Wed, 16 Oct 2019 at 08:46, George Nistor <george.n(a)l4b-software.com> wrote: > > Hi Lava users, > > My adb is not running on the host but in the lxc container lava creates at runtime. > I have tried to put also an: adb kill-server command before starting vts but I got the same error. > > The lava log looks like this: > <LAVA_SIGNAL_STARTRUN 0_device-helpers 219_1.8.4.1> > + cd /home/android-vts/tools > + adb kill-server > Received signal: <STARTRUN> 0_device-helpers 219_1.8.4.1 Starting test > lava.0_device-helpers (219_1.8.4.1) Skipping test definition patterns. > * server not running * > + ./vts-tradefed > Android Vendor Test Suite 9.0_R2 (eng.l4b.20190906.094644) Use > \"help\" or \"help all\" to get more information on running commands. > 10-16 07:30:15 E/adb: ADB server didn't ACK > 10-16 07:30:15 E/ddms: 'adb start-server' failed -- run manually if > necessary > 10-16 07:30:15 E/adb: * failed to start daemon * > 10-16 07:30:15 E/adb: error: cannot connect to daemon > [udev_trigger-lxc-hikey-test-219-07:30:23] device /dev/bus/usb/001/008 > added > > george > > > -----Original Message----- > From: Milosz Wasilewski <milosz.wasilewski(a)linaro.org> > Sent: Tuesday, October 15, 2019 17:11 > To: George Nistor <george.n(a)l4b-software.com> > Cc: lava-users(a)lists.lavasoftware.org > Subject: Re: [Lava-users] VTS does not start because of the adb > > Do you have adb server running on the host? If so, please kill it and > try again. As with LoTR - there is only one adb server to rule them > all :) > > milosz > > On Tue, 15 Oct 2019 at 15:01, George Nistor <george.n(a)l4b-software.com> wrote: > > > > Hello Lava users, > > > > > > > > Thanks to Tim Jaaks for previous problem I reported. I managed to configure default external shared folder for the lava lxc container. > > > > > > > > However, > > > > I try to run VTS from Lava but after displaying initial string with VTS I get an error saying adb server could not start. I have tried restart, no success. The adb seems to be installed in the container. > > > > Does anyone know how to solve this error? > > > > > > > > + ./vts-tradefed > > > > Android Vendor Test Suite 9.0_R2 (eng.l4b.20190906.094644) > > > > Use \"help\" or \"help all\" to get more information on running commands. > > > > 10-15 13:45:22 E/adb: ADB server didn't ACK > > > > 10-15 13:45:22 E/ddms: 'adb start-server' failed -- run manually if > > necessary > > > > 10-15 13:45:22 E/adb: * failed to start daemon * > > > > 10-15 13:45:22 E/adb: error: cannot connect to daemon > > > > [udev_trigger-lxc-hikey-test-214-13:45:29] device > > /dev/bus/usb/001/005 added > > > > > > > > > > > > > > > > The adb is put in tlcx deploy > > > > > > > > actions: > > > > - deploy: > > > > namespace: tlxc > > > > timeout: > > > > minutes: 5 > > > > to: lxc > > > > packages: > > > > - adb > > > > - fastboot > > > > - wget > > > > - unzip > > > > - default-jre > > > > os: debian > > > > > > > > > > > > george > > > > _______________________________________________ > > Lava-users mailing list > > Lava-users(a)lists.lavasoftware.org > > https://lists.lavasoftware.org/mailman/listinfo/lava-users > _______________________________________________ > Lava-users mailing list > Lava-users(a)lists.lavasoftware.org > https://lists.lavasoftware.org/mailman/listinfo/lava-users

5 years, 6 months

2
3
0 0

any vland users out there?

by Milosz Wasilewski

Hi, Today I started looking at our LAVA testing setup and discovered that vland has been stopped for the last 7 months. Since no one complained I assume it's either working flawlessly in production environments or it's not needed. If there are any vland users, please reply to this message so I know that fixing our testing setup is not a waste of time. milosz

5 years, 6 months

1
0
0 0

lxc container rootfs not found

by Fedusiv Ilya

Hello, LAVA Team! I tried to run test on lxc, but get error message: Lxc container rootfs not found Inline: Job description: https://pastebin.com/5ibuzqD9 Errors log: https://pastebin.com/6X8c548r Git: Job description https://pastebin.com/iffydGYc Error log: https://pastebin.com/62pXctFd Ilya

5 years, 6 months

2
1
0 0

Potential issue with multiple uarts

by Nick Schutt

Hi, I have a board with 4 uarts connected to a lava worker via ser2net. LAVA is giving me some strange results when I try to use two uarts (uart0 and uart2) in the same testcase. The results are not consistent. Sometimes it works, but most of the time it gives an error: KeyError: 'uart2' At the end of the job, LAVA prints: LAVABug: This is probably a bug in LAVA, please report it.error_type: Bug error_msg: 'uart2' case: job result: fail definition: lava <http://lava-master.sw.nxp.com/results/testcase/16283386> ---- The connection parts of the device definition are: % set connection_list = ['uart0', 'uart1', 'uart2', 'uart3'] %} {% set connection_tags = {'uart0': ['primary', 'telnet']} %} {% set connection_commands = {'uart0': 'telnet localhost 7001', 'uart1': 'telnet localhost 7002', 'uart2': 'telnet localhost 7003', 'uart3': 'telnet localhost 7004'} %} The job uses two boots; one primary to boot non-POSIX to uboot, then it switches to 'uart2' to access another processor. The job seems to work fine if I define only two uarts: % set connection_list = ['uart0', 'uart1'] %} {% set connection_tags = {'uart0': ['primary', 'telnet']} %} {% set connection_commands = {'uart0': 'telnet localhost 7001', 'uart1': 'telnet localhost 7003 } %} Thank you, Nick

5 years, 6 months

2
1
0 0

VTS does not start because of the adb

by George Nistor

Hello Lava users, Thanks to Tim Jaaks for previous problem I reported. I managed to configure default external shared folder for the lava lxc container. However, I try to run VTS from Lava but after displaying initial string with VTS I get an error saying adb server could not start. I have tried restart, no success. The adb seems to be installed in the container. Does anyone know how to solve this error? + ./vts-tradefed Android Vendor Test Suite 9.0_R2 (eng.l4b.20190906.094644) Use \"help\" or \"help all\" to get more information on running commands. 10-15 13:45:22 E/adb: ADB server didn't ACK 10-15 13:45:22 E/ddms: 'adb start-server' failed -- run manually if necessary 10-15 13:45:22 E/adb: * failed to start daemon * 10-15 13:45:22 E/adb: error: cannot connect to daemon [udev_trigger-lxc-hikey-test-214-13:45:29] device /dev/bus/usb/001/005 added The adb is put in tlcx deploy actions: - deploy: namespace: tlxc timeout: minutes: 5 to: lxc packages: - adb - fastboot - wget - unzip - default-jre os: debian george

5 years, 6 months

2
3
0 0

repeat in lava not work

by cnspring2002

actions: - repeat: count: 2 I just add above in job, and web submit validator told me: Job submission error: extra keys not allowed @ data['actions'][1]['repeat'] Does it still work now?

5 years, 6 months

3
4
0 0

unable to run vts because adb-start-server

by George Nistor

Hello Lava users, Thanks to Tim Jaaks for previous problem I reported. I managed to configure default external shared folder for the lava lxc container. However, I try to run VTS from Lava but after displaying initial string with VTS I get an error saying adb server could not start. I have tried restart, no success. The adb seems to be installed in the container. Does anyone know how to solve this error? + ./vts-tradefed Android Vendor Test Suite 9.0_R2 (eng.l4b.20190906.094644) Use \"help\" or \"help all\" to get more information on running commands. 10-15 13:45:22 E/adb: ADB server didn't ACK 10-15 13:45:22 E/ddms: 'adb start-server' failed -- run manually if necessary 10-15 13:45:22 E/adb: * failed to start daemon * 10-15 13:45:22 E/adb: error: cannot connect to daemon [udev_trigger-lxc-hikey-test-214-13:45:29] device /dev/bus/usb/001/005 added The adb is put in tlcx deploy actions: - deploy: namespace: tlxc timeout: minutes: 5 to: lxc packages: - adb - fastboot - wget - unzip - default-jre os: debian george

5 years, 6 months

1
0
0 0

is lxc shared folder possible?

by George Nistor

Hi Lava users, For my test, instead of downloading android-vts.zip archive from git I decided it will be used from a location on a machine which hosts Lava. The question is: Is it possible to make like a shared folder for the lxc container lava has created? Or is any other way to access directly from the lxc container a folder on the host machine? If so, how should be done? george

5 years, 6 months

2
1
0 0

Re: [Lava-users] lava job without any flashing on a real device

by George Nistor

Yes, In my case the only way I could make lava to see the fastboot device was via running pre-power-command, and I run a script (I customized device descriptor to run a this script as pre-power-command) which does: 1. Power Off Wait 5s 2.Power On Wait 30s 3. Login as root Wait 5s 4. echo reboot bootloader. # make it go in fastboot mode Immediately after this script runs, the udev rule is triggered and device id added (seen from Lava). Otherwise the reboot does not work for me. The line: nice lxc-attach -n lxc-hikey-test-186 -- fastboot -s xxxxxxx reboot gives timeout. Because the device is not seen. To make the job work without any flashing I removed the - deploy section which does flashing entirely For my case: I have added to boot this section protocols: lava-lxc: - action: fastboot-boot request: pre-power-command timeout: minutes: 5 george The full job I cannot post due to company policy with confidentiality on projects. -----Original Message----- From: Milosz Wasilewski <milosz.wasilewski(a)linaro.org> Sent: luni, 14 octombrie 2019 15:58 To: George Nistor <george.n(a)l4b-software.com> Subject: Re: lava job without any flashing on a real device Could you send the question to ML? I don't know why adb is not enough. Maybe LAVA waits for udev event? milosz On Mon, 14 Oct 2019 at 13:51, George Nistor <george.n(a)l4b-software.com> wrote: > > I have managed after all to do it with a job like this: > My problem was to be able to run pre-power-command before boot, to make lava to see the fastboot device - trigger that python script lxc-device-add. > > > -----Original Message----- > From: Milosz Wasilewski <milosz.wasilewski(a)linaro.org> > Sent: Monday, October 14, 2019 15:02 > To: George Nistor <george.n(a)l4b-software.com> > Subject: Re: lava job without any flashing on a real device > > There was a feature called 'dummy deploy' but I can't find it any more. Did you try simply removing 'deploy' action? This should do the trick but you will need transfer_overlay in your boot section. > > milosz > > On Mon, 14 Oct 2019 at 12:33, George Nistor <george.n(a)l4b-software.com> wrote: > > > > Hi Milosz, > > > > > > > > I have a small question: > > > > Is it possible to run a lava job without any deploy – flashing sequence on a real device? > > > > > > > > I attach the job I’m working on. > > > > > > > > george

5 years, 6 months

1
0
0 0

Comparing output within a job execution between reboots

by Diego Russo

Hello, I have a job with the following flow: 1) deploy the DUT 2) boot the DUT 3) while booting, I need to capture a string: it is the version/timestamp of BL2. For example: NOTICE: BL2: v2.1(release):v2.1-232-g89a4d26-dirty NOTICE: BL2: Built : 04:06:44, Sep 25 2019 4) perform an update of the BL2 5) reboot the device 6) while booting the second time, I need to capture again the version/timestamp 7) Compare the 2 strings: if they are different, the test passes. How can I do 3) 6) and 7) with LAVA? Thanks -- 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.

5 years, 6 months

3
7
0 0

Lava does not do DUT login

by George Nistor

Hello Lava users, I have a Lava job, with the following section: - boot: namespace: target prompts: - 'root@xxxxx:~#' auto_login: login_prompt: 'xxxxx login:' username: root timeout: minutes: 5 method: fastboot and Lava does not complete with 'root' to do autologin. After 5 mins it give me timeout autologin. Even if I run the job and waited till the login prompt comes as output in Lava and do a echo 'root' > /dev/ttyUSB2 still Lava detects timeout autologin. (even if the devices successfully logs in - I have sent the string 'root' 2 times from the terminal). [ 25.440854] audit: type=1325 audit(1564586870.989:25): table=filter family=2 entries=8 BMW xxxxx 19w32.5-1-2 mgu22 ttyMSM0 mgu22 login: root 7[r[999;999H[6nroot@xxxxx:~# root -sh: root: not found root@mgu22:~# [ 79.848385] firmware cdsp.mdt: _request_firmware_load: firmware state wait timeout: rc = -110 [ 79.857777] subsys-pil-tz 8300000.qcom,turing: cdsp: Failed to locate cdsp.mdt(rc:-11) auto-login-action timed out after 231 seconds The complete lava job is here. https://pastebin.com/MeV1AyeR Where is the mistake I do? george

5 years, 6 months

2
1
0 0

ODROID-N2: Installation & configuration help

by Malcolm Brooks

Hi All, I am installing an ODROID-N2 board into our LAVA setup. I see that there is support for ODROID-X2 and ODROID-XU3 in the LAVA codebase, but no mention of ODROID-N2. Before I start, I wanted to know if anyone has successfully installed an ODROID-N2 in LAVA? Does it work with the existing support added for the other variants? Are there any specific bits of hardware I will need to use and/or device dictionary settings I need to ensure are set before I can get the board up and running? Regards, Malcolm 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.

5 years, 6 months

2
1
0 0

lava-server-gunicorn worker crashes

by Dean Birch

Hi, We've recently had an issue with our LAVA instance (version 2019.05.post1), where a long running LAVA job which had a large log file led to instabilities when serving web content. The large job was seemingly causing lava-server-gunicorn workers to use up more memory than was available, leading to workers crashing and then restarting. This led to all the workers processing the large jobs most of the time, while other requests would only be served once the workers restarted. This led to the webpages being served extremely slowly and lavacli usage timing out (if a larger timeout was not set). We had "LOG_SIZE_LIMIT": 3 set in our /etc/lava-server/settings.conf, and we did have the message on that job page for "*This log file is too large to view"*, but it seems that some requests were still attempting to process some aspect of the job causing these worker crashes. Is there any other settings that might need to be set in order to cope with long running jobs with large log files that might help with this situation? Before we look into this any further, does anyone know if this is fixed with a newer version of LAVA? Has anyone had any similar issues with their instances? Thanks, Dean

5 years, 6 months

2
1
0 0

lava inside a VM, lxc container on host machine can't get an IP address

by George Nistor

Hi Lava users, I have a problem with the lxc container which is created on the host machine, by getting an IP address. Lava is installed in a, VM with Debian stretch. Has anyone experienced this problem before? Or anyone any idee why lxc does not get the ip? Here are the logs: lava-dispatcher, installed at version: 2019.09+stretch start: 0 validate Start time: 2019-09-24 12:29:39.318789+00:00 (UTC) lxc, installed at version: 1:2.0.7-2+deb9u2 Validating that file:///usr/mgu22/mgu22-19w32.5-1-2-bmw-image-mgu22-sa8155.rootfs.ext4 exists validate duration: 0.07 definition: lava result: pass case: validate start: 1 lxc-deploy (timeout 00:05:00) [tlxc] start: 1.1 lxc-create-action (timeout 00:05:00) [tlxc] nice lxc-create -q -t debian -n lxc-hikey-test-13 -- --release stretch --mirror http://mirror.bytemark.co.uk/debian --packages systemd,systemd-sysv Container created successfully end: 1.1 lxc-create-action (duration 00:01:22) [tlxc] level: 1.1 case: lxc-create-action definition: lava result: pass namespace: tlxc duration: 82.21 extra: ... start: 1.2 lxc-create-udev-rule-action (timeout 00:03:38) [tlxc] device info file '/var/lib/lava/dispatcher/tmp/13/lxc-create-udev-rule-action-y0_d19aq/device-info.yaml' created with: [{'board_id': '7d4452a4'}] udev rules file '/var/lib/lava/dispatcher/tmp/13/lxc-create-udev-rule-action-nj_8pzv0/100-lava-lxc-hikey-test-13.rules' created ACTION=="add", ATTR{serial}=="7d4452a4", RUN+="/usr/share/lava-dispatcher/lava_lxc_device_add.py --lxc-name lxc-hikey-test-13 --device-node $name --job-id 13 --logging-url tcp://localhost:5555" '/etc/udev/rules.d/100-lava-lxc-hikey-test-13.rules' symlinked to '/var/lib/lava/dispatcher/tmp/13/lxc-create-udev-rule-action-nj_8pzv0/100-lava-lxc-hikey-test-13.rules' nice udevadm control --reload-rules udev rules reloaded. end: 1.2 lxc-create-udev-rule-action (duration 00:00:00) [tlxc] start: 1.3 boot-lxc (timeout 00:03:38) [tlxc] nice lxc-start -n lxc-hikey-test-13 -d output: Wait until 'lxc-hikey-test-13' state becomes RUNNING nice lxc-info -sH -n lxc-hikey-test-13 output: RUNNING output: 'lxc-hikey-test-13' state is RUNNING Wait until 'lxc-hikey-test-13' gets an IP address nice lxc-info -iH -n lxc-hikey-test-13 output: nice lxc-info -iH -n lxc-hikey-test-13 output: nice lxc-info -iH -n lxc-hikey-test-13 output: nice lxc-info -iH -n lxc-hikey-test-13 output: nice lxc-info -iH -n lxc-hikey-test-13 output: nice lxc-info -iH -n lxc-hikey-test-13 output: Here is my Lava job: https://pastebin.com/kiLbnjAX

5 years, 7 months

1
0
0 0

job submit error

by veera brahmam

Hi All, i am new LAVA framework i am trying to submit my first job , but error like "Invalid definition: extra keys not allowed @ data['job_timeout']" i am attaching screen shot & file. Can someone please help me to solve this issue Thanks Veera

5 years, 7 months

2
2
0 0

Change overlay directory

by Ilya Fedusiv

Is it possible to change directory on device of overlay and all LAVA stuff for example to /tmp/ ? By default now it is / Ilya

5 years, 7 months

2
5
0 0

Sending information containing whitespaces with lava-send

by Tim Jaacks

Hello everyone, I am trying to send some information containing whitespaces via lava-send. Obviously this is not supported. Is this a bug or by design? I tried the following command: lava-send my-message my-variable="some string with whitespaces" Which produces the following output: <LAVA_SEND_DEBUG lava_multi_node_send preparing Tue Aug 27 15:02:41 CEST 2019> <LAVA_SEND_DEBUG _lava_multi_node_send started Tue Aug 27 15:02:41 CEST 2019> <LAVA_MULTI_NODE> <LAVA_SEND my-message my-variable=some> <LAVA_SEND_DEBUG _lava_multi_node_send finished Tue Aug 27 15:02:41 CEST 2019> <LAVA_SEND_DEBUG lava_multi_node_send finished Tue Aug 27 15:02:41 CEST 2019> Received Multi_Node API <LAVA_SEND> messageID: SEND-my-message lava-multinode lava-send 1 key value pair(s) to be sent. Handling signal <LAVA_SEND {"timeout": 360, "request": "lava_send", "messageID": "my-message", "message": {"my-variable": "some"}}> So obviously the string is truncated on the first whitespace. Is there any possibility to send a string containing whitespaces to another node? 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 WE MAKE IT YOURS! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun

5 years, 7 months

2
3
0 0

Test commands

by Ilya Fedusiv

# root@device:~# # lava-test-shell: Wait for prompt ['root@device:~#'] (timeout 00:05:00) # Using /lava-133 export SHELL=/bin/bash root@device:~# export SHELL=/bin/bash export SHELL=/bin/bash . /lava-133/environment root@device:~# . /lava-133/environment . /lava-133/environment -sh: .: can't open '/lava-133/environment' Will listen to feedbacks from 'tlxc' for 1 second /lava-133/bin/lava-test-runner /lava-133/0 root@device:~# /lava-133/bin/lava-test-runner /lava-133/0 Test shell timeout: 10s (minimum of the action and connection timeout) /lava-133/bin/lava-test-runner /lava-133/0 -sh: /lava-133/bin/lava-test-runner: not found Device is successfully booted and logged in. But I cant run any commands. Why lava running this command? : . /lava-133/environment And how it downloads to device. Ilya

5 years, 7 months

2
1
0 0

Fastboot reboot-bootloader

by Ilya Fedusiv

Hi! Lava as default at beginning runs that command: nice fastboot -s 261a1c5d reboot-bootloader Is it possible to avoid this step? Dont run this command Ilya

5 years, 7 months

2
15
0 0

Re: [Lava-users] Server returning wrong job id

by Fabiano Ferronato

Hi Milosz, Please take a look at the first message of this thread. There are 2 different information for this error. First, this COMMA error happens when I'm trying to access the URL (LAVA WebU), manually inserting the job_id in a browser, and not through the code. Second, the previous code is returning: lavac.server.NoSuchJob: No such job: 68271.0 Even though this job_id is been returned by the LAVA server. Thanks Em seg, 2 de set de 2019 às 11:32, Milosz Wasilewski < milosz.wasilewski(a)linaro.org> escreveu: > On Mon, 2 Sep 2019 at 10:26, Fabiano Ferronato <fabiferro(a)hotmail.com> > wrote: > > > > Hi Milosz, > > > > I still couldn't update the server but, just to clarify, the mentioned > job pasted in URL is 68271.0 as we can see in the error message: > > > > URL : http://lava.server.net/scheduler/job/68271.0 > > > > > Trying to access LAVA WebUI using the jobid (68271.0) > > > > And then some process is translating that jobid into a comma " , " : > > > > > Reverse for 'lava.scheduler.job.detail' with arguments '('',)' not > found. 1 pattern(s) tried: ['scheduler/job/(?P<pk>[0-9]+|[0-9]+\\.[0-9]+)$'] > > > > Otherwise, a really not existent jobid in the URL, let's say 99999.9, > results in "404 Not found". > > > > Here is the job submission code: > > > > try: > > job_id = self._server.scheduler.submit_job(job_data) > > if not isinstance(job_id, list): > > job_id = [job_id] > > return job_id > > > > And than the job_id is used to get job details: > > > > try: > > return self._server.scheduler.job_details(job_id) > > scheduled.job_details expects a string: > https://master.lavasoftware.org/api/help/#scheduler.job_details > > If I understand your code correctly you're passing a list to this > function. Serialized list will contain "," character. > > milosz > > > > > Best Regards, > > Fabiano > > > > Em sex, 23 de ago de 2019 às 16:25, Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> escreveu: > >> > >> I don't think there was a problem with 2018.10 with this feature. > >> Reading the error message I think you pasted "," character in the URL > >> so the pattern didn't match. As you can see in the regex, "." is there > >> and I don't recall any issues with multinode jobs then. Anyway, even > >> if this is a bug it won't be fixed in 2018.10. When you migrate to > >> latest version and you hit the same problem something can be done. > >> > >> If you can post full script you're using I can try on latest master > >> and see what happens. > >> > >> milosz > >> > >> On Fri, 23 Aug 2019 at 13:10, Fabiano Ferronato <fabiferro(a)hotmail.com> > wrote: > >> > > >> > Hi Milosz, thanks for your answer. > >> > > >> > Yes, it is a multinode job. > >> > This is a known bug on version 2018.10? I need to install the new > version and keep pipe lines running until I get the error to answer you. > >> > > >> > Fabiano > >> > > >> > Em qui, 22 de ago de 2019 às 18:58, Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> escreveu: > >> >> > >> >> On Thu, 22 Aug 2019 at 17:30, Fabiano Ferronato < > fabiferro(a)hotmail.com> wrote: > >> >> > > >> >> > Hi, > >> >> > we have a LAVA test setup working for some time. Automated > pipelines are running tests on different devices in parallel. > >> >> > After updating to version 2018.10+stretch and changing to in-line > job definitions we started to get some sporadic errors. > >> >> > > >> >> > The error message shows up after jobs are submitted and the return > from the submission is then used to ask for server job details: > >> >> > > >> >> > res = lava_server.submit_job(lava_test_job_description) > >> >> > for entry in res: > >> >> > job_details = lavasrv.job_details(entry) > >> >> > ... > >> >> > > >> >> > Resulting in the following error: > >> >> > > >> >> > lib/python3.5/site-packages/lavac/server.py", line 272, in > job_details > >> >> > raise get_server_error(error, job_id) > >> >> > lavac.server.NoSuchJob: No such job: 68271.0 > >> >> > >> >> are you submitting a multinode job? Does this also happen in more > >> >> recent version of LAVA (like 2019.07)? > >> >> > >> >> milosz > >> >> > >> >> > > >> >> > > >> >> > Trying to access LAVA WebUI using the jobid (68271.0): > >> >> > > >> >> > 500 Internal Server Error > >> >> > Reverse for 'lava.scheduler.job.detail' with arguments '('',)' not > found. 1 pattern(s) tried: ['scheduler/job/(?P<pk>[0-9]+|[0-9]+\\.[0-9]+)$'] > >> >> > > >> >> > Can you give me a hint about this error? > >> >> > > >> >> > Thanks! > >> >> > > >> >> > _______________________________________________ > >> >> > Lava-users mailing list > >> >> > Lava-users(a)lists.lavasoftware.org > >> >> > https://lists.lavasoftware.org/mailman/listinfo/lava-users > >> > > >> > _______________________________________________ > >> > Lava-users mailing list > >> > Lava-users(a)lists.lavasoftware.org > >> > https://lists.lavasoftware.org/mailman/listinfo/lava-users >

5 years, 7 months

2
1
0 0

Fastboot device Connection

by Ilya Fedusiv

Hi! I'm using lava from debian stretch. I try flash image by fastboot. At that step job just stuck and util timeout of 10 minutes. nice fastboot -s '261a1c5d' flash persist /var/lib/lava/dispatcher/tmp/15/fastboot-deploy-7xj200yq/persist/persist.ext4 If run command from terminal fastboot -s 261a1c5d flash persist /tmp/persist.ext4 device is flashed in 3 seconds It looks like, that LAVA doesnt see my device. Job desc : https://pastebin.com/ZNeS71Ev Device desc: https://pastebin.com/rYRyEnjy Job log : https://pastebin.com/fH0u3bUb I know, that for fastboot better to work with lxc. I also tried with lxc. And it stuck on the same place. Job log with lxc : https://pastebin.com/RnZLNfvN Ilya

5 years, 7 months

2
5
0 0

Lava job with local testcase

by Vladut Magas

Hello, I have a question regarding running a test that I have on my host machine inside a Lava job. Basically, I start Lava and try to submit a job through: Scheduler/Submit The job description looks like this: device_type: qemu job_name: qemu amd64 LTP timeouts: job: minutes: 120 action: minutes: 120 connection: minutes: 120 priority: medium visibility: public metadata: source: https://ci.linaro.org/view/lava-ci/job/lava-debian-stable-amd64-vm/ path: https://git.linaro.org/ci/job/configs.git/blob/HEAD:/lava-debian-stable-amd… build-readme: https://images.validation.linaro.org/snapshots.linaro.org/components/lava/s… build-console: https://ci.linaro.org/view/lava-ci/job/lava-debian-stable-amd64-vm/console build-log: http://images.validation.linaro.org/snapshots.linaro.org/components/lava/st… # CONTEXT_BLOCK context: arch: amd64 # ACTIONS_BLOCK actions: - deploy: timeout: minutes: 120 to: tmpfs images: rootfs: image_arg: -drive format=raw,file={rootfs} url: https://images.validation.linaro.org/snapshots.linaro.org/components/lava/s… sha256sum: 4ab50cc69fc61faa9bf48edada8bc1a317247f77ced5a815f40e75cef1d62cc7 compression: gz # BOOT_BLOCK - boot: method: qemu media: tmpfs timeout: minutes: 120 prompts: - "root@debian:" auto_login: login_prompt: "login:" username: root - test: timeout: minutes: 120 definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: apache-server description: "server installation" os: - debian scope: - functional run: steps: Here I would like to have my test.Something like: - make - ./home/user/folder/mytest from: inline name: apache-server path: inline/apache-server.yaml Can you maybe give me a short example on how to do that? I tried using the "inline" keyword, but to no avail. Best regards, Emanuel-Vladut Magas L4B Software, Iasi, Romania E-mail: vladut.m(a)l4b-software.com [cid:37eb12b3-1085-46f2-8e9a-e636f5edc7d8]

5 years, 7 months

2
1
0 0

Test Job bulk canceling from admin does not work in 2019.09

by Stevan Radakovic

We've just discovered that the bulk canceling of test jobs in LAVA admin does not work. Issue in gitlab: https://git.lavasoftware.org/lava/lava/issues/310 We will fix this asap and roll it out with next release or hotfix, whichever comes first. A workaround is to either use XMLRPC API or cancel jobs one at a time. Cheers, -- Stevan Radaković | LAVA Engineer Linaro.org <www.linaro.org> │ Open source software for ARM SoCs

5 years, 7 months

1
0
0 0

Power time measurements

by Denis HUMEAU

Dear Lava users, I'm looking for a way to measure, with Lava, time measurements between some power modes. Let's say the time between two messages : - Standby exit trigger - Actual standby exit from the kernel The constraint is that we can't rely on kernel timestamps (frozen during standby) and the power process implies not only kernel but also boot stages. We can only rely on the time spent between two specific messages in the console. Basically, if it was done without Lava, we'd use a tool like grabserial. Do you have any clue on what can be done? Best regards,

5 years, 7 months

2
3
0 0

500 Internal Server Error

by Ilya Fedusiv

Hi! Problem, that I'm receiving Internal Server Error Error log of django : https://pastebin.com/9dxTi0nm Log of apache : https://pastebin.com/SSwyHymT I've started working with LAVA. I installed on VirtualBox Debian stretch, as recommended. I want lava-server lava-master lava-slave on one machine and work locally. I provided next step for installing LAVA: Add this lines to /etc/apt/sources.list deb http://deb.debian.org/debian stretch-backports main deb https://apt.lavasoftware.org/release stretch-backports main root# wget https://apt.lavasoftware.org/lavasoftware.key.asc root# apt-key add lavasoftware.key.asc root# apt-get update root# apt -t stretch-backports install lava-server root# a2dissite 000-default root# a2enmod proxy root# a2enmod proxy_http root# a2ensite lava-server.conf root# service apache2 restart After that I changed some parameters as written here : https://validation.linaro.org/static/docs/v2/installing_on_debian.html#usin… to run locally I checked variables value http://54.68.224.33/static/docs/v2/pipeline-debug.html#displaying-current-s… It is similar to what I set up. root# lava-server manage check --deploy ?: (security.W012) SESSION_COOKIE_SECURE is not set to True. Using a secure-only session cookie makes it more difficult for network traffic sniffers to hijack user sessions. ?: (security.W016) You have 'django.middleware.csrf.CsrfViewMiddleware' in your MIDDLEWARE, but you have not set CSRF_COOKIE_SECURE to True. Using a secure-only CSRF cookie makes it more difficult for network traffic sniffers to steal the CSRF token. I've read that mailing list post: https://lists.lavasoftware.org/pipermail/lava-users/2018-March/000884.html So I download http://cdn-fastly.deb.debian.org/debian/pool/main/d/django-tables/python3-d… and dpkg -i to downgrade python3-django-tables2 restart everything. This didnt helped. Ilya.

5 years, 7 months

3
3
0 0

Multinode job: how can I assure that all devices are on the same worker?

by Tim Jaacks

Hello again, I have several test cases where we use LAVA multinode to test hardware and software interfaces externally. E.g. we have an SFTP server running on our DUT. In order to test that, we submit a test using two nodes: 1. The DUT 2. An LXC container The LXC device connects to the DUT via SFTP and uploads a file. Both sides determine the MD5 sum and the DUT compares them. This works as long as both the DUT and the LXC device are in the same network (or at least can reach each other via the network). Now there are more test cases which require additional hardware connections between the worker and the DUT, e.g. a serial interface test. The serial interface on the DUT is connected via an RS232-USB converter to the worker. The LXC can access this converter and send or receive data from the serial interface. This works as long as the LXC is running on the expected worker the serial interface of the DUT is connected to. As we are growing our lab, we will add more workers to our setup. There will be LXC devices on all of the workers. When submitting such a multinode job, which relies on hardware connections between the DUT and the worker, how can I make sure that the LXC part of the job is scheduled on an LXC device on the correct worker? 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 WE MAKE IT YOURS! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun

5 years, 7 months

3
16
0 0

UART connection parameters

by Dupont, Louis [2]

Hi, I'm looking into LAVA and I figured I'd give it a try by flashing a frdm-k64f MCU board and parse its output (the board behaves as a USB to UART adapter through /dev/ttyACM0 at 115200bps). I created the board instance as: {% extends 'frdm-k64f.jinja2' %} {% set board_id = '0240000048824e45004a700add89001a8761000097969900' %} {% set usb_mass_device = '/dev/disk/by-id/usb-MBED_VFS_0240000048824e45004a700add89001a8761000097969900-0:0' %} I'm able to launch a job (frdm-k64f.job) but LAVA complains and returns: Invalid job data: ["Invalid device configuration - missing 'commands'"] So I went looking for an example and found this<https://git.lavasoftware.org/fabo/lava/blob/bc44750733f57de09909f45ba7e65fa…> which defines something called connection_commands as: {% set connection_commands = {'usb0': 'telnet lab-slave-0 7115'} %} Based on the documentation<https://docs.lavasoftware.org/lava/connections.html> I'm under the impression that the slave/dispatcher is expected to momentarily open a telnet server on port 7115 and forward the output of the serial port through that server to be retrieved by a client implemented by the master. If I match the example the dispatcher flashes the board, but a telnet server is never launched on the slave. It's not surprising as at no point did I specify a tty or a baud rate for the dispatcher to connect to the board in order and launch something like: socat TCP-LISTEN:7115,fork,reuseaddr FILE:/dev/ttyACM0,b115200,raw When I sit on the slave and manually launch the command the master successfully connects to TCP port 7115. Problem is it does so after the board outputted its results (and obviously it's not the right way to do it). So I have 3 questions: * How should a UART connection be specified (/dev/ttyACM0, 115200bps) to LAVA? * Once the UART connection specified, will the dispatcher buffer the board's output until it is retrieved by the master? * Why does LAVA rely on a telnet channel instead of the existing zmq channel to forward the output of the board from the slave to the master? Thanks

5 years, 7 months

3
2
0 0

DUT in recovery mode under LAVA

by Diego Russo

Hello, We have few device types in our LAVA instance that use ums mechanism to be deployed. This has worked well so far but we have now the need to test secure boot flow (BL1, BL2...) and we cannot rely anymore in u-boot for deploying them. Assuming we have the HW in place to put the DUT in recovery mode, how can we achieve this via LAVA? Do you have an existent example where you automate the recovery mode of a board? Thanks -- 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.

5 years, 7 months

2
4
0 0

Accessing physical worker devices from LXC

by Tim Jaacks

Hello everyone, I have the following entry in my lxc device dictionary: {% set static_info = [ {'board_id': 'FTXTBHMA'}, ] %} This adds my USB-serial converter installed on the worker machine to the LXC. It appears correctly in the LXC: root@lxc-generic-remote-5937:~# ls -la /dev/ttyUSB* crw-r----- 1 root root 188, 0 Jul 30 13:15 /dev/ttyUSB0 crw-r----- 1 root root 188, 1 Jul 30 13:15 /dev/ttyUSB1 crw-r----- 1 root root 188, 2 Jul 30 13:15 /dev/ttyUSB2 crw-r----- 1 root root 188, 3 Jul 30 13:15 /dev/ttyUSB3 I cannot read from or write to it, though: root@lxc-generic-remote-5937:~# cat /dev/ttyUSB0 cat: /dev/ttyUSB0: Operation not permitted This does not seem to be a permission issue in the LXC, it fails even if I set all permissions: root@lxc-generic-remote-5937:~# chmod a+rwx /dev/ttyUSB0 root@lxc-generic-remote-5937:~# cat /dev/ttyUSB0 cat: /dev/ttyUSB0: Operation not permitted Does anybody have an idea what is missing here? 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 WE MAKE IT YOURS! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun

5 years, 8 months

3
5
0 0

device_description

by Fedusiv Ilya

Hello, LAVA Team! I have question about device description. I have problems with *pre_power_command* If I don't use requests : pre_power_command in my job description, i get error, that no request implementation. So in my case, I need to switch device to fastboot mode by sending command via serial connection. And I decided, that pre_power_command is better solution for me. Cause before fastboot deploying by setting up this command I will switch device's mode. And here I stuck, cause I received error message: no pre_power_command implementation. Device description: https://pastebin.com/FLhGUnyH Job description: https://pastebin.com/Ts6VUXZe Error log: https://pastebin.com/9jXvjxZb best regards, Ilya

5 years, 8 months

1
0
0 0

Adding device

by Fedusiv Ilya

Hi, LAVA Team! I'm trying to add my new device. It must be flashed by fastboot. To turn device into fastboot mode, I need to write "reboot bootloader" via serial connection. I have tried set soft_reboot_command = ['reboot bootloader'] and received error message lava-lxc protocol: FAILED executing 'lxc-attach -n lxc-hikey-test-4 -- adb reboot bootloader' Ilya

5 years, 8 months

1
0
0 0

Server returning wrong job id

by Fabiano Ferronato

Hi, we have a LAVA test setup working for some time. Automated pipelines are running tests on different devices in parallel. After updating to version 2018.10+stretch and changing to in-line job definitions we started to get some sporadic errors. The error message shows up after jobs are submitted and the return from the submission is then used to ask for server job details: res = lava_server.submit_job(lava_test_job_description) for entry in res: job_details = lavasrv.job_details(entry) ... Resulting in the following error: lib/python3.5/site-packages/lavac/server.py", line 272, in job_details raise get_server_error(error, job_id) lavac.server.NoSuchJob: No such job: 68271.0 Trying to access LAVA WebUI using the jobid (68271.0): 500 Internal Server Error Reverse for 'lava.scheduler.job.detail' with arguments '('',)' not found. 1 pattern(s) tried: ['scheduler/job/(?P<pk>[0-9]+|[0-9]+\\.[0-9]+)$'] Can you give me a hint about this error? Thanks!

5 years, 8 months

3
4
0 0

access target board with adb from LAN tu run CTS

by George Nistor

Hi Milosz, I am using the Raspberry Pi 3 B+ board as a real target. It has AOSP Pie 9 on it and runs. I would be interested now, to see like you said if I could run CTS,VTS on the board and omit deploy section. What should I put in the boot section as method: Would be the same fastboot or another method? I ask because the board is connected to LAN (and not over USB). Is it ok just to omit deploy section? In other words how would Lava know to access the board on ADB over its IP. Where should I set this info? Example section (Milosz CTS&VTS example): https://pastebin.com/hBn0pq6U

5 years, 8 months

2
1
0 0

to: iso-installer and flash with adb using wifi

by George Nistor

Hi Lava Users, I have decided to continue using a real device: a Raspberry Pi 3 B+. Because I have an iso with Android 9 Pie, to flash the board I want to use deploy: to: iso-installer The question I'm having is: Is it possible to use this mode to flash the board with ADB via Wifi? (The board, I connected wifi to our router and I am able to connect with adb using wifi) (The board does not have USB/OTG interface so the only option is to use ADB on wifi.) What I try to achieve is deploy the image I have - iso one (flash), with adb using wifi, and run as tests CTS and VTS. george -----Original Message----- From: Milosz Wasilewski <milosz.wasilewski(a)linaro.org> Sent: Wednesday, August 21, 2019 11:27 AM To: George Nistor <george.n(a)l4b-software.com> Cc: lava-users(a)lists.lavasoftware.org Subject: Re: [Lava-users] old comercial phones supported by Lava On Wed, 21 Aug 2019 at 08:00, George Nistor <george.n(a)l4b-software.com> wrote: > > Hi, > > But I do not understand exactly for example if I can use a Nexus5x; the device is in the list of supported devices Steve McIntyre sent me. > Milosz Wasilewski said I cannot use it with Lava due to the lack of possibility to force power cycle on them (via serial interface - USB). > our current use case doesn't require power cycling the device. It uses the same OS build and tests are executed in chroot environment. This is pretty specific setup for the use case (doesn't require changing kernel). > To be able to use it requires hw modification of the device? yes, you need to be able to forcibly power cycle the device. With battery inside the phone this isn't possible, so you have to remove battery and replace it with power supply you can turn off. > > What we want to have for the moment is a real device (ex, Nexus 5) on which to run Tradef with Lava. What is your use case? Are you testing tradefed (ex CTS) changes and stick with the same Android build or do you test Android (kernel, libraries, etc) changes? If it's the former you might be lucky and use existing nexus5 support. If you want to test android using CTS, HW modification is necessary. milosz > > george > > -----Original Message----- > From: Steve McIntyre <steve.mcintyre(a)linaro.org> > Sent: Tuesday, August 20, 2019 8:51 PM > To: George Nistor <george.n(a)l4b-software.com> > Cc: lava-users(a)lists.lavasoftware.org > Subject: Re: [Lava-users] real devices supported by Lava by default > > Hi George, > > On Tue, Aug 20, 2019 at 12:54:21PM +0000, George Nistor wrote: > > > >I have a question regarding real devices supported by Linaro Lava. > > > >Besides these dev boards I found here : > >https://validation.linaro.org/static/ > >docs/v2/standard-armmp-ramdisk-bbb.html#standard-known-devices > > > >Are any other real devices supported in Lava by default? (any > >commercial phone for example Nexus 5)? > > There's a huge set of supported devices. If you don't already have > LAVA installed, the easiest way to find the list is by looking at the > set of device type configurations at > > > https://git.lavasoftware.org/lava/lava/tree/master/etc/dispatcher-conf > ig/device-types > > Cheers, > -- > Steve McIntyre steve.mcintyre(a)linaro.org > <http://www.linaro.org/> Linaro.org | Open source software for ARM > SoCs > > > _______________________________________________ > Lava-users mailing list > Lava-users(a)lists.lavasoftware.org > https://lists.lavasoftware.org/mailman/listinfo/lava-users

5 years, 8 months

2
2
0 0

lxc problem

by Fedusiv Ilya

It appears always, right from the start of the job. lxc is installed on my dispatcher. Job description https://pastebin.com/5g15YrWy DUT description: https://pastebin.com/bTKdaM5i I know dut description is not full, but I want do step by step, firstly run lxc on device. Maybe you can give some advice about DUT desc. I'm using fastboot flash for few partitions after that fastboot reboot flash_cmds_order - it is order of flashing partition fastboot_sequence - what is it? Do you have some manual about this parameters description, cause have not found it on your website. And one more question, lxc deployed on dispatcher, right? Best regards, Ilya Fedusiv

5 years, 8 months

2
8
0 0

old comercial phones supported by Lava

by George Nistor

Hi, But I do not understand exactly for example if I can use a Nexus5x; the device is in the list of supported devices Steve McIntyre sent me. Milosz Wasilewski said I cannot use it with Lava due to the lack of possibility to force power cycle on them (via serial interface - USB). To be able to use it requires hw modification of the device? What we want to have for the moment is a real device (ex, Nexus 5) on which to run Tradef with Lava. george -----Original Message----- From: Steve McIntyre <steve.mcintyre(a)linaro.org> Sent: Tuesday, August 20, 2019 8:51 PM To: George Nistor <george.n(a)l4b-software.com> Cc: lava-users(a)lists.lavasoftware.org Subject: Re: [Lava-users] real devices supported by Lava by default Hi George, On Tue, Aug 20, 2019 at 12:54:21PM +0000, George Nistor wrote: > >I have a question regarding real devices supported by Linaro Lava. > >Besides these dev boards I found here : >https://validation.linaro.org/static/ >docs/v2/standard-armmp-ramdisk-bbb.html#standard-known-devices > >Are any other real devices supported in Lava by default? (any >commercial phone for example Nexus 5)? There's a huge set of supported devices. If you don't already have LAVA installed, the easiest way to find the list is by looking at the set of device type configurations at https://git.lavasoftware.org/lava/lava/tree/master/etc/dispatcher-config/de… Cheers, -- Steve McIntyre steve.mcintyre(a)linaro.org <http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

5 years, 8 months

2
1
0 0

real devices supported by Lava by default

by George Nistor

Hello Lava users, I have a question regarding real devices supported by Linaro Lava. Besides these dev boards I found here : https://validation.linaro.org/static/docs/v2/standard-armmp-ramdisk-bbb.htm… Are any other real devices supported in Lava by default? (any commercial phone for example Nexus 5)? george

5 years, 8 months

3
2
0 0

LXC-START

by Fedusiv Ilya

Hello, LAVA Team! I'm trying to implement own device description. Run with standard fastboot singlenode with lxc. And received error: lava-dispatcher, installed at version: 2019.03+stretchstart: 0 validateStart time: 2019-08-19 15:01:03.367020+00:00 (UTC)validate duration: 0.00result: fail definition: lava case: validate <http://localhost:10080/results/testcase/8>Cleaning after the jobRoot tmp directory removed at /var/lib/lava/dispatcher/tmp/2InfrastructureError: The Infrastructure is not working correctly. Please report this error to LAVA admins.error_msg: Cannot find command 'lxc-start' in $PATH error_type: Infrastructure result: fail definition: lava case: job <http://localhost:10080/results/testcase/9> Best regards, Ilya Fedusiv

5 years, 8 months

2
1
0 0

Help on kernelci integration

by Xiaofeng Ren

Anyone can help to provide some suggestion about following kernelci integration problem: We setup one kernelci in our infrastructure and deploy LAVA master and slave as well. kernelci can support build, LAVA can also work to run automation test. We use the lava-boot-v2.sh (jenkins job in kernelci-core project ) to trigger lava test, but we found that both boot report or test report can't be synchronized to kernelci dashboard. It will report json format error, may I know whether we need follow boot schema or test schema defined in kernelci (https://api.kernelci.org/schema-boot.html and https://api.kernelci.org/schema-test.html) to create one report, then trigger LAVA callback function to post one request? Following is callback definition in https://github.com/kernelci/kernelci-core/blob/master/templates/base/kernel…. Do we need customize this callback if we want to post request for boot and test result? Any suggestion will be appreciated. {%- if callback %} notify: criteria: status: finished callback: {%- if callback_type == 'custom' %} url: {{ callback_url }} {%- else %} url: {{ callback_url }}/callback/{{ callback_name }}?lab_name={{ lab_name }}&status={STATUS}&status_string={STATUS_STRING} {%- endif %} method: POST dataset: {{ callback_dataset }} token: {{ callback }} content-type: json {% endif %}

5 years, 8 months

2
2
0 0

Adding new device

by Fedusiv Ilya

Hello LAVA Team! Found in manual about adding new device, at begin better to write to you. Device is: aarch64 Flashing via fastboot (have partition table list) Device has serial debug connection. For flashing using next commands: fastboot flash <partition name> <path> ... ... fastboot set_active a fastboot reboot To turn device into fastboot mode need to enter command in serial debug. Best regards, Ilya Fedusiv

5 years, 8 months

2
1
0 0

running CTS and VTS from lxc against an qemu target with AOSP

by George Nistor

Hi Lava Users, I am trying to create a target with qemu running android as an ISO image. The job I intend to write is to run CTS and VTS on a qemu target with android. But I receive error when submitting. Could anyone help me telling me which are my mistakes I do with the job? None of the deployment strategies accepted your deployment parameters, reasons given: qemu-nfs: "to" is not "nfs" lxc: "to" parameter is not "lxc" overlay: 'overlay' not in the device configuration deploy methods removeable: "media" was not "sata", "sd", or "usb" fastboot: "to" parameter is not "fastboot" tftp: "to" parameter is not "tftp" nfs: "to" parameter is not "nfs" images: "to" parameter is not "tmpfs" flasher: 'flasher' not in the device configuration deploy methods docker: 'docker' not in the device configuration deploy methods uboot-ums: "to" parameter is not "u-boot-ums" ssh: "ssh" is not in the device configuration deploy methods download: "to" parameter is not "download" iso: "iso" was not in the parameters recovery-mode: 'recovery' not in the device configuration deploy methods mps: "mps" was not in the device configuration deploy methods nbd: "to" parameter is not "nbd" vemsd: "to" parameter is not "vemsd" device_type: qemu job_name: george_ISO_6 timeouts: job: minutes: 120 action: minutes: 120 connection: minutes: 120 priority: medium visibility: public # CONTEXT_BLOCK context: arch: amd64 # ACTIONS_BLOCK actions: - deploy: timeout: minutes: 120 to: iso-installer images: rootfs: url: https://osdn.net/frs/redir.php?m=cznic&f=android-x86%2F69704%2Fandroid-x86-… sha256sum: 71e3cd7e7151fbc7e9bb29be10e337b2545586d3ef173c5ae8c07d13bf595732 # BOOT_BLOCK - boot: method: qemu-iso media: media=cdrom,readonly timeout: minutes: 20 connection: serial

5 years, 8 months

2
3
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users