lava-users

lava-users@lists.lavasoftware.org

1 participants
919 discussions

Lava Test/Dev Environment Setup Best Practices

by Swapnil Tilaye

Hi Team Currently for the developing and running of the lava tests, we always run on the Lava master machine through lavacli. But we would like to skip the part of the running the tests from the lava master machine while developing, testing and triaging the tests written in the lava. We only want to run tests which are tested correctly to be run on through ci/cd on the lava master and for development, triaging we want to only use the lava-worker and board. We only want to use the lava master only through CI/CD. [cid:86e0132a-a975-4d04-9f31-9a89237339d8] Is there any way to run tests directly from the lava worker instead of going through lava master. I tried "lava-test-shell" and "lava-dispatcher" but it didnt work for me. Can I use the lava api for developing and triaging the test scripts? Can you please recommend the best practice or setup for developing, testing and triaging the tests written in the lava? so that anyone can run, develop or modify tests quickly and make sure its successful and then only it can run through the lava master machine. Regards, Swapnil Tilaye

1 year, 1 month

Possible regression: LAVA breaks initrds/ramsisks with attached microcode

by Florian Bezdeka

Hi all, over the last days I was trying to bring up a setup where we simply try to boot up a kernel and initrd combination that is provided by Debian "as is". Sounds trivial at first but I ran into a problem with the initrd: The initrd contains some microcode, shipped as prepended uncompressed archive. The microcode is added because the intel-microcode package was installed during image generation. When such an initrd enters the LAVA machinery, where the initrd is first unpacked and later re-packed the file gets corrupted in a way that the kernel is unable to unpack/use it. The end result was that NFS boot did not work as the mounting of the rootfs did not take place. Interestingly there is no error message, not within the unpack/repack step in LAVA and the kernel does not complain later during the boot sequence either. To disable the LAVA unpack/repack sequence I had to modify my deploy action. Setting install_overlay and install_modules [2] to false seems to qualify as workaround: - deploy: timeout: minutes: 15 to: tftp kernel: url: <kernel-url> ramdisk: url: <initrd-url> install_overlay: false install_modules: false Looking at the initramfs-tools implementation [1] I think that something similar is missing in LAVA. Does that make sense? Ideas / comments? Best regards, Florian [1] https://gitlab.com/lava/lava/-/blob/master/lava_dispatcher/actions/deploy/a… [2] https://salsa.debian.org/kernel-team/initramfs-tools/-/blob/master/unmkinit… -- Siemens AG, Technology Linux Expert Center

1 year, 1 month

"Proxy Error" message while loading more size log from LAVA jobs

by koti

Hi, We are seeing below the "Proxy Error" message while loading log size logs from the LAVA job . Is there any solution to load a long size log file from a LAVA job ? [image: image.png]

1 year, 1 month

Compare builds (from SQUAD (backend is LAVA)) gives the message "No tests to display"

by koti

Hi , I am comparing the LAVA tests from the below SQUAD lkft Android project URL . But I am getting the message "No Tests to display". https://qa-reports.linaro.org/_/comparebuilds/?project=android-lkft-benchma… Can someone let me know the solution to compare the tests in different builds from the project "android-lkft-benchmarks <https://qa-reports.linaro.org/android-lkft-benchmarks/>" ? Note: 1. But, we are able to get compare test list for LKFT project builds. But not for Android build as I mentioned above email. Do not know the reason. https://qa-reports.linaro.org/_/comparebuilds/?project=lkft/linux-stable-rc… Regards, Koti

1 year, 2 months

lava-users

by irreallich

1 year, 2 months

Can we use custom baud rates in lava framework to get logs on serial console

by Nagendra Singamsetti

Hi All, My board is configured at 55000 baud for serial communication. Can work only at this baud, Can we use lava with this configuration to get console prints in test method. Default lava is supporting telnet with standard baud rates. Is there a way to make 55000 baud for uart and get prints on lava. Regards Nagendra S

1 year, 2 months

tftp deploy action: images

by Michael Peddie

Hi, In a previous thread where I was getting help to do a serial connection, I also needed help with the deploy action towards the end, so I'm just continuing that here. I have been trying to do a deploy action for a couple of days now, and have been unsuccessful thus far. The obvious first hurdle is the image URLs for the various things needed for a tftp deploy action. I have compiled a u-boot kernel, and a DTB came with it, and I managed to sort the few errors I got with those (for now at least). I'm not sure modules are necessary, but I can figure that out later. The biggest issue I'm having is with the ramdisk. There are many resources online for creating a ramdisk, but it is just a space in the ram for things to be stored temporarily (which I don't mind). But this does not work for lava, as it seems to require a file. I have tried compressing the directory created, and passing that, but because it is still just a directory lava won't accept it after I start the job. So I'm assuming I have to acquire some kind of image somehow, how can I do this? Is there an online source I can download from? Or if I have to make it, how? Best regards, Michael

1 year, 2 months

how to boot up -> catch uart log -> deploy test by ssh -> run test by ssh?

by irreallich＠126.com

The process I expect is: 1. test board restart 2. catch the bootup log by serial port 3. deploy the test suit (test script) by ssh 4. run test case by ssh or uart (ssh is better) 5. These are concentrated in one yaml and all logs are captured. Now I try to restart the test board by below code, it works, board reboot successfully device: actions: deploy: methods: {% if flasher_reset_commands %} flasher: commands: {{ flasher_reset_commands }} {% endif %} test yaml - deploy: timeout: minutes: 30 to: flasher images: kernel: url: http://10.19.207.190/static/docs/v2/contents.html#contents-first-steps-using But if I add ssh to deploy in the device file, the yaml remains unchanged and I will be prompted with device BAD. device as blow: {# device_type: orinnew #} {% extends 'base.jinja2' %} {% block body %} actions: deploy: methods: {% if flasher_reset_commands %} flasher: commands: {{ flasher_reset_commands }} {% endif %} ssh: options: {{ ssh_options }} # primary connections get this from the device dictionary. # secondary connections get this from the lava-multinode protocol support. host: "{{ ssh_host|default('') }}" port: {{ ssh_port|default(22) }} user: "{{ ssh_user|default('root') }}" identity_file: "{{ ssh_identity_file }}" boot: connections: serial: methods: ssh: minimal: {% endblock body %} 1. Where did I go wrong to cause this problem? 2. Every time you paste code, there will be formatting problems. How to paste code in this mail list? It has an effect similar to markdown.

1 year, 2 months

Trouble adding raspberry pi device

by Daniel Jensen

Hey all, I am currently trying to add a raspberry pi device to my lava installation however it keeps saying that I have an invalid device configuration. This is the device dictionary {% extends 'bcm2711-rpi-4-b.jinja2' %} {% set connection_list = ['uart0']%} {% set connnection_commands = {'uart0': 'telnet 10.60.2.209 7002'}%} {% set connection_tags = {'uart0': ['primary','telnet']}%} {% set power_off_command = 'python /hbus_power.py off' %} {% set hard_reset_command = 'python /hbus_power reboot' %} {% set power_on_command = 'python /hbus_power on' %} Is there anything I'm doing wrong with this? or any other ideas as to what could be wrong?

1 year, 2 months

Serial Connection

by Michael Peddie

Hi, I have started trying to connect my DUT and run tests via serial. I'm not sure if it's a me issue, or a documentation issue, but I can't seem to puzzle it together. My DUT is connected to my worker via serial, and I've configured my ser2net.yaml file (docs say it's a .config, but I found no such thing) with both the provided example and something based on what was already in there. The problems arise in the job definition, and device dictionary. I've made a (pretty much) blank device template which extends base-uboot, and does nothing else. The device dictionary defines power_off_command, power_on_command, soft_reboot, and the connection_(list, commands, and tags). There is also the baud rate and console device However, I've also seen some device templates use a root device instead or alongside console device, what's the difference? Whenever I use my worker IP for the telnet command, I get connection refused, but if I use the DUT IP the connection times out after 2 minutes. I can connect to the device using minicom, so I don't think the serial connection is bad, and I have no problems using SSH on the device and other systems connected to my network. The only information I have on the device is that it's ARMv5TEJ, it has a custom kernel and runs on otherwise custom hardware. Below is my device dict: {% extends 'test-template.jinja2' %} {% set power_off_command = 'python /power.py off' %} {% set soft_reboot_command = 'reboot' %} {% set power_on_command = 'python /power.py on' %} {% set connection_list = ['uart0'] %} {% set connection_commands = {'uart0': 'telnet dispatcher01 7001'} %} {% set connection_tags = {'uart0': ['primary', 'telnet']} %} {% set console_device = 'ttyUSB0' %} {% set baud_rate = 115200 %} My questions are: - Difference between root_device and console_device in device dictionary/template? - Do I set the telnet command to use my worker IP or my DUT IP? - Is there something other than telnet I'm meant to or can use? - How am I actually meant to configure the ser2net.yaml? - How do I define the test job for serial to execute commands on the DUT? Regards, Michael

1 year, 2 months

← Newer
1
2
3
4
5
6
7
...
92
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users