lava-users

lava-users@lists.lavasoftware.org

950 discussions

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

6 years, 12 months

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]

6 years, 12 months

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

6 years, 12 months

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,

6 years, 12 months

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.

6 years, 12 months

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

6 years, 12 months

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

7 years

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.

7 years

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

7 years

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

7 years

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users