lava-users

lava-users@lists.lavasoftware.org

1 participants
919 discussions

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

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

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

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

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

unable to run vts because adb-start-server

by George Nistor

5 years, 6 months

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

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

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

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

← Newer
1
...
34
35
36
37
38
39
40
...
92
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users