lava-users March 2019

lava-users@lists.lavasoftware.org

11 participants
12 discussions

External worker devices in LXC / connection to DUTs

by Tim Jaacks

Hello, we are trying to add external interfaces on the worker to connect with the DUTs, for example a 4-port USB-to-RS232 converter. Our DUTs have multiple RS232 ports which shall be tested using this remote interface. We have already figured out how to integrate this hardware into the LAVA environment, so that it can be used within the LAVA LXC (using static_info in the device dictionary, resulting in the four /dev/ttyUSB* devices being visible there). First question: We need multiple of these converters attached to the worker. How do we integrate these into LAVA? They all have the same board_id, vendor_id and product_id. If I specify the board_id in the device dictionary multiple times, the device is still added only once. Second question: We need a way to specify to which of the /dev/ttyUSB* ports a certain RS232 port of the DUT is connected. The place where I would assume to put such information is the device dictionary. But how can we access this information within a LAVA test shell? The documentation specifies some similar mechanism for energy probes: https://validation.linaro.org/static/docs/v2/admin-lxc-deploy.html?highligh… It says "Devices which are not directly attached to the worker can also be supported, for example energy probes which communicate over the network". As far as I can tell from the code, though, this seems to be a hard-coded feature without any possibility of adding other custom hardware. Is that correct? If yes, why isn't there a generic mechanism to supply static_info from the device dictionary in the LAVA test shell? Or is there? How can we implement our scenario described above using LAVA? 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

5 years, 9 months

query to retrieve Lava errors

by Denis HUMEAU

After getting stats on my setup robustness, the step forward is have a complete view on the lava errors we meet in incomplete jobs. >From what I see in incomplete jobs, my intention is to query on test suite lava and the name "job". In the query builder, if I use test suite as condition model, I can't use the job field name. Do you have any advice on how to proceed? Denis

5 years, 9 months

device type alias redesign

by Milosz Wasilewski

Hi, There is an idea of device type 'alias' in LAVA. I don't quite understand what the use case for the current implementation was [1]. I tried using it but it wasn't very useful. My use case is that I need to submit jobs to a device type with different device type name. This is used to align device type naming between different labs in a bigger project (kernelci.org in this case). So the questions I have about current implementation: - is there anyone using current implementation? - if current implementation is used, how much trouble would it cause to change the behaviour? Change in behaviour is quite intrusive and will require database migration. [1] https://master.lavasoftware.org/static/docs/v2/glossary.html#term-alias Regards, milosz

5 years, 11 months

LAVA Ansible playbooks

by Karsten Tausche

Hi, Are the Ansible playbook for setting up LAVA available somewhere? There is an old migrated issue on GitLab [1] which is closed, but the link to an implementation in there is dead. Is that playbook only internally available for Linaro? Is there anything you could share? It looks like many people are moving to Docker in the moment, but that's not an option for us (at least not for dispatchers), as we need LXC for Android testing. Cheers, Karsten [1] https://git.lavasoftware.org/lava/lava/issues/27

5 years, 12 months

record measurement

by Frank, Matthias

Hi, I want to measure some output values of test cases. I have a shell script which run stress-ng, parse it's output and exports some measurement variables. How can I record theses variables? I tried to use lava-test-case -shell myscript.sh -result pass -measurement $VAR1 -unit unit but no values are recorded. Maybe this is the wrong approach, but how can I do this in the correct way? Matthias

5 years, 12 months

What happened if different worker link to different coordinator in one lava instance?

by cnspring2002

As title: What happened if different worker link to different coordinator in one lava instance for multinode job?

6 years

query about lava usage for MCU like solution

by Hake Huang

Hi Sirs, Does LAVA support MCU like system? Which usually using a debugger to download image to a MCU internal flash, and get uart result? Regards, Hake

6 years

jobs using notify with tokens, resubmit as different user

by Kevin Hilman

How can you have more than one LAVA user have the same token secret (e.g. for a notify callback.)? Example use case: - LAVA job with notify callbacks using token names - submited as user "bob", token names of "bob" map to actual token secrets - job fails - user "lab-admin" fixes some lab issues, re-submits job - job passes, but callbacks fail because tokens are associated with user "bob" Since the re-submitted job runs as user "lab-admin", the same token names and corresponding secrets don't exist. Naively, user "lab-admin" tries to copy the token secrets from user "bob" keeping the same token names, but this fails saying that "secret already exists". Why can't different users have the same secrets? I haven't looked at the code, but this limitation kind of suggests that the secret itself is the key in the db, which would prevent multiple secrets of the same. Kevin

6 years

kexec boot mechanism

by Hemanth K V

Hello Lava-users, Do we have any sample reference yaml job definition which has booting the target with kexec method. Thanks, Hemanth.

6 years

Build information in metadata

by Frank, Matthias

Hello lava users, I use in a test job linuximage, rootfs and dtb from file server location retrieved via http. These files are nightly build from Jenkins. The file links are static so I can use new images within the same test job definition. Jenkins generates also a build information text file with commit IDs an so on. How can I integrate the content of this file in the job metadata or job result log? Using metadata: build-readme: <link> in the job definition is not possible because the link is stable over different build, but the file content is changing. The DUT has no access to the file location because it is in an isolated network. Is there a way to cat the file content on the worker to metadata or job result? Greetings, Matthias

6 years

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users March 2019