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

by MARVIN Trijasse

Hello, As a new member of DI team from Schneider electric I have an issue when installing my lava agent on our raspberry pi. I followed this procedure https://collaborate.linaro.org/pages/viewpage.action?pageId=118293253#Getti… as I run the docker_compose build I get this error ERROR: Service 'lava-dispatcher' failed to build : no matching manifest for linux/arm/v7 in the manifest list entries (see image in attachment) Marvin Trijasse

4 years, 3 months

2
1
0 0

Worker/master version mismatch

by Philippe Mazet (OSS)

Hi All, Since 2020.09 it appears that workers using a version different than the master are refusing to start. Would it be possible to relax this constraint? With workers spread all over the world in different places, it is hard to synchronize master and slaves upgrades. Also, we have always run with workers versions <= master version, without a single problem. So it would be great to allow version mismatch, and maybe print a simple warning when version differs? Thanks, Philippe

4 years, 3 months

2
3
0 0

Regarding lava installation facing problem

by Satishkumar Rajguru

Hi All, this is the first time I am communicating with the lava community. I am facing a problem with the lava installation. I need step by step installation procedure and after installation one example demo for the understanding purpose. (send all steps because I am first time using the lava ) in that, I am facing a problem when I type the command $sudo apt-get install lava-server then getting the following error message : --------------------------------------------------------------------------------------------------------------------------------------------------------- File "/usr/lib/python3/dist-packages/lava_rest_app/v02/routers.py", line 22 from import views ^ SyntaxError: invalid syntax migration dpkg: error processing package lava-server (--configure): installed lava-server package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: lava-server E: Sub-process /usr/bin/dpkg returned an error code (1) ------------------------------------------------------------------------------------------------------------------------------------------------------------- please send the information from the first command of installation to the last command of installation which I need to use. Note: I am using Ubuntu 18.04.5 LTS. Thank You.

4 years, 3 months

2
1
0 0

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, 3 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, 3 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, 3 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, 3 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, 3 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, 4 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, 5 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, 5 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, 5 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, 5 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, 5 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, 5 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, 5 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, 5 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, 6 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, 6 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, 6 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, 6 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, 6 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, 7 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, 8 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, 8 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, 8 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, 8 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, 9 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, 9 months

3
5
0 0

LTP and some other tests in QEMU

by 黄璐

4 years, 9 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, 9 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, 9 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, 9 months

3
7
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users