lava-users

lava-users@lists.lavasoftware.org

2 participants
944 discussions

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

6 years, 7 months

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

6 years, 7 months

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 %}

6 years, 7 months

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

6 years, 7 months

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

6 years, 7 months

Re: [Lava-users] running commands locally from a Lava job

by George Nistor

Hi Lava users, I am using the sample you sent me last week to run tradefed: https://gist.github.com/mwasilew/e6e80a351d43388b1c3342098012ec Until we have a real device to run on Tradefed we decided to use it with qemu, so the question is: 1. How do we deploy android on qemu via Lava? 2. How to boot android via lava? Do you have any sample job for the above questions? george ________________________________ From: George Nistor Sent: Thursday, August 8, 2019 2:19:05 PM To: Vladut Magas <vladut.m(a)l4b-software.com>; Inon Sharony <inon.s(a)l4b-software.com>; Yair Podemasky <yair.p(a)l4b-software.com> Cc: Andreas Schl?ter <andreas.s(a)l4b-software.com>; Ilya Fedusiv <ilya.f(a)l4b-software.com> Subject: FW: [Lava-users] running commands locally from a Lava job Here is the answer I have just received from Linaro via their mail-list. They say it is not a good idea to build tradefed with lava, but it can be used in the scenario to run TF from an LXC container - they have said. Tradefed should be built from outside Lava. george -----Original Message----- From: Milosz Wasilewski <milosz.wasilewski(a)linaro.org> Sent: Thursday, August 8, 2019 2:07 PM To: George Nistor <george.n(a)l4b-software.com> Cc: lava-users(a)lists.lavasoftware.org Subject: Re: [Lava-users] running commands locally from a Lava job On Thu, 8 Aug 2019 at 11:50, George Nistor <george.n(a)l4b-software.com> wrote: > > Thanks for the answers, > > 1. What do you mean by "with LXC container acting as a host side ". It is an LXC container on the machine where Lava runs and inside this containes runs Tradefed? yes, exactly. Here is an example job definition: https://gist.github.com/mwasilew/e6e80a351d43388b1c3342098012ec5c I can't share the actual job and logs as there are passwords included. milosz > 2. Where can I find an example of these Jobs? Could you help me with an link, or sample jobs? > > george > > -----Original Message----- > From: Milosz Wasilewski <milosz.wasilewski(a)linaro.org> > Sent: Thursday, August 8, 2019 1:29 PM > To: George Nistor <george.n(a)l4b-software.com> > Cc: lava-users(a)lists.lavasoftware.org > Subject: Re: [Lava-users] running commands locally from a Lava job > > I would say it's a bad idea. LAVA is not meant for building stuff. It can do that but you will need to hack around quite a lot. Secondly IIUC you need to have dependency between build and run steps. If you want to implement this using LAVA this implies multi-node job. There is no other way LAVA will manage dependencies and timings between executions. So this is getting pretty complicated already. > > LAVA is already running tradefed jobs (CTS and VTS) using real hardware and it's a pretty common use case. There are 2 implementations of this. One is using single node job with LXC container acting as a host side. Other is using multinode and can shard tests between multiple devices. However tradefed packages are built outside of lava and downloaded before job starts. > > To sum up, I think what you're trying to do is not best suited for LAVA. However it might be possible given some effort spent on experimenting. > > milosz > > On Thu, 8 Aug 2019 at 11:20, George Nistor <george.n(a)l4b-software.com> wrote: > > > > Yes > > For one job to build tradefederation from inside a docker container. > > For the second job to run Google TradeFederation from the docker container. > > > > Would be that possible with Lava? > > > > george > > > > -----Original Message----- > > From: Milosz Wasilewski <milosz.wasilewski(a)linaro.org> > > Sent: Thursday, August 8, 2019 1:16 PM > > To: George Nistor <george.n(a)l4b-software.com> > > Cc: lava-users(a)lists.lavasoftware.org > > Subject: Re: [Lava-users] running commands locally from a Lava job > > > > George, > > > > Do I understand correctly you would like to use LAVA as a building tool? > > > > milosz > > > > On Thu, 8 Aug 2019 at 10:47, George Nistor <george.n(a)l4b-software.com> wrote: > > > > > > Hi Lava users, > > > > > > > > > > > > Is it possible to run commands inside a lava job test-section, locally, from a Lava Job? > > > > > > Ex: > > > > > > cd /media/sh_shared_folders > > > > > > docker build -t tradefed . > > > > > > > > > > > > We have the following setup: > > > > > > A machine with Linux Ubuntu; > > > an Oracle Virtual Box VM on the machine with a Xubuntu distro > > > image inside the VM we have created 3 Docker containers: > > > > > > one with the Jenkins > > > second one with Lava > > > third is created for the purpose of running Google TradeFederation > > > against the Android device > > > > > > > > > > > > (The AOSP source tree is available to the VM via shared_folders > > > and the docker container has also access to it. (via docker run -v > > > dir_host:dir_container) ) > > > > > > > > > > > > What we what to achieve is to have 2 jobs in Lava : > > > > > > one for building the Docker image for the purpose of building > > > TradeFederation inside > > > > > > Ex. Running these commande locally: > > > > > > source > > > ./build/make/envsetup.sh > > > > > > lunch > > > <device-target> > > > > > > make > > > tradefed-all -j8 > > > > > > > > > > > > second using the above image, instantiate, create a container > > > which should run TradeFederation against the android device > > > connected to the machine > > > > > > > > > > > > What I need is to be able to run commands locally inside the VM (on Xubuntu distro) from a Lava job. For these we have to somehow not send the command to qemu but run them locally. > > > > > > Is this possible? If yes, how can we achieve this? > > > > > > > > > > > > George Nistor > > > > > > _______________________________________________ > > > 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

6 years, 7 months

running commands locally from a Lava job

by George Nistor

Hi Lava users, Is it possible to run commands inside a lava job test-section, locally, from a Lava Job? Ex: cd /media/sh_shared_folders docker build -t tradefed . We have the following setup: * A machine with Linux Ubuntu; * an Oracle Virtual Box VM on the machine with a Xubuntu distro image * inside the VM we have created 3 Docker containers: * one with the Jenkins * second one with Lava * third is created for the purpose of running Google TradeFederation against the Android device (The AOSP source tree is available to the VM via shared_folders and the docker container has also access to it. (via docker run -v dir_host:dir_container) ) What we what to achieve is to have 2 jobs in Lava : * one for building the Docker image for the purpose of building TradeFederation inside Ex. Running these commande locally: source ./build/make/envsetup.sh lunch <device-target> make tradefed-all -j8 * second using the above image, instantiate, create a container which should run TradeFederation against the android device connected to the machine What I need is to be able to run commands locally inside the VM (on Xubuntu distro) from a Lava job. For these we have to somehow not send the command to qemu but run them locally. Is this possible? If yes, how can we achieve this? George Nistor

6 years, 7 months

Re: [Lava-users] Testjob state is cancelling

by Remi Duraffort

Hello, I'm asking if the corresponding lava-slave is still working properly. You can see that on the web interface in the workers page. By the way, which version are you using? Le mar. 6 août 2019 à 16:25, Gumansingh, Smita <Smita_Gumansingh(a)mentor.com> a écrit : > Yes Remi, > > Corresponding testjob is still running on device from last 3 days after it > got canceled it from GUI. Testjob state is showing canceling > and my device state is showing Running. > > test-hardware | x86 | running | 15696 > > > Thanks & Regards, > Smita Gumansingh > ------------------------------ > *From:* Remi Duraffort <remi.duraffort(a)linaro.org> > *Sent:* Tuesday, August 6, 2019 6:26 PM > *To:* Gumansingh, Smita > *Subject:* Re: [Lava-users] Testjob state is cancelling > > Hello, > > are you sure that the corresponding lava-slave is still running? > > > Rgds > > Le mar. 6 août 2019 à 09:11, Gumansingh, Smita < > Smita_Gumansingh(a)mentor.com> a écrit : > >> Hi all, >> >> I cancelled a test job but it still running on my device and showing >> testjob state as “cancelling”. Is there any way to restart the device ,so >> that I can submit some other job . >> >> Killing the specific job id on lava-master using lava-cli also not >> solving the problem. >> >> >> >> *Regards,* >> >> *Smita Gumansingh* >> >> >> >> [image: cid:image001.jpg@01D2E5A8.A6033460] >> >> >> >> Senior test Engineer, EPS PBU Software QA/Dev Ops >> >> Mentor Graphics, >> >> Nalapad Brigade Centre, Unit No:301 & 302 >> >> Mahadevapura, Bengaluru, Karnataka 560048, India >> >> Office: +91 8067624338 |Cell: +91 9538349245 >> >> www.mentor.com >> >> >> _______________________________________________ >> Lava-users mailing list >> Lava-users(a)lists.lavasoftware.org >> https://lists.lavasoftware.org/mailman/listinfo/lava-users > > > > -- > Rémi Duraffort > LAVA Team, Linaro > -- Rémi Duraffort LAVA Team, Linaro

6 years, 7 months

usb serial not seen in LXC container

by Axel Lebourhis

Hi all, I'm running CTS tests on Android 9, with LAVA. I noticed the CTS module CtsUsbTests failed because of the error: "usb serial != adb serial expected:<[]> but was:<[a266fa0a5c85d6ee]>" This module is a hostsidetest, and checks if usb serial matches adb serial by running "lsusb -v" on the host and checking the iSerial returned by the command. ( https://android.googlesource.com/platform/cts/+/refs/heads/master/hostsidet… ) And this test fails when I run it with LAVA so I checked on my local PC and the test passes. Indeed, if I run the command "lsusb -v" I get this output for iSerial: iSerial 3 351d5a0a5c85d936 The third field is the adb serial, so it matches well. So I suspected the LXC container to not give the usb serial. So I checked directly in the container and after running "lsusb -v" I got: iSerial 3 The adb serial is missing. So, do you know a way to make the LXC see correctly the usb serial ? Regards, Axel

6 years, 7 months

uboot-ums with bmap-tools

by Diego Russo

Hello, We've been using uboot-ums deploy mechanism for quite some time but we really want to move away from dd and star using bmap-tools. I guess lava does not support it (yet) but I was wondering if there is a way where we can use uboot-ums with bmap-tools. 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.

6 years, 7 months

← Newer
1
...
40
41
42
43
44
45
46
...
95
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users