lava-users

lava-users@lists.lavasoftware.org

1 participants
919 discussions

by gemad＠outlook.com

Hello, Is there a standard way to reboot the ECU by calling the reboot command defined in the device type (hard_reset_command), between test case, so we are sure the tests are not impacting each other? Thanks.

1 year, 4 months

[SSL: CERTIFICATE_VERIFY_FAILED] self signed certificate

by Ankit Gupta

Hi All, I am setting an HTTPS instance of LAVA, I can access the LAVA UI and am able to log in as well. I am using a self-signed SSL certificate. I have added *URL="https://172.16.60.178/ <https://172.16.60.178/>"* in the /etc/lava-dispatcher/lava-worker file and restarted the service. It's giving me the below error. *2023-10-30 07:10:47,383 ERROR -> server error: code 5032023-10-30 07:10:47,383 DEBUG --> HTTPSConnectionPool(host='172.16.60.178', port=443): Max retries … [View More]

1 year, 4 months

Bug using SSH as primary connection

by Sebastian Lucas

Hello everyone, There seems to be a bug in LAVA. I was on version 2022.04 and have also tried 2023.03. Both versions have the same bug. The same configurations works in a 2018 build of LAVA on an old machine. I am trying to connect to an always on board via ssh. The healthcheck is failing with this error : lava-dispatcher, installed at version: 2023.03<https://10.1.52.17/scheduler/job/8857#L1>start: 0 validate<https://10.1.52.17/scheduler/job/8857#L2>Start time: 2023-04-12 14:… [View More]07:00.373707+00:00 (UTC)<https://10.1.52.17/scheduler/job/8857#L3>Traceback (most recent call last): File "/usr/lib/python3/dist-packages/lava_dispatcher/job.py", line 198, in validate self._validate() File "/usr/lib/python3/dist-packages/lava_dispatcher/job.py", line 183, in _validate self.pipeline.validate_actions() File "/usr/lib/python3/dist-packages/lava_dispatcher/action.py", line 190, in validate_actions action.validate() File "/usr/lib/python3/dist-packages/lava_dispatcher/actions/deploy/ssh.py", line 81, in validate if "serial" not in self.job.device["actions"]["deploy"]["connections"]: KeyError: 'connections' <https://10.1.52.17/scheduler/job/8857#L4> validate duration: 0.00<https://10.1.52.17/scheduler/job/8857#results_244238>case: validate case_id: 244238 definition: lava result: fail <https://10.1.52.17/results/testcase/244238><https://10.1.52.17/scheduler/job/8857#L6>Cleaning after the job<https://10.1.52.17/scheduler/job/8857#L7>Root tmp directory removed at /var/lib/lava/dispatcher/tmp/8857<https://10.1.52.17/scheduler/job/8857#L8>LAVABug: This is probably a bug in LAVA, please report it.<https://10.1.52.17/scheduler/job/8857#results_244239>case: job case_id: 244239 definition: lava error_msg: 'connections' error_type: Bug result: fail<https://10.1.52.17/results/testcase/244239> The health check looks like this: job_name: SSH check timeouts: job: minutes: 10 action: minutes: 2 priority: medium visibility: public actions: - deploy: timeout: # timeout for the connection attempt seconds: 30 to: ssh os: oe - boot: timeout: minutes: 2 prompts: ['root@(.*):~#'] method: ssh connection: ssh - test: timeout: minutes: 5 definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: smoke-tests-basic description: "Basic smoke test" run: steps: - lava-test-case linux-linaro-ubuntu-pwd --shell pwd - lava-test-case linux-linaro-ubuntu-uname --shell uname -a - lava-test-case linux-linaro-ubuntu-vmstat --shell vmstat - lava-test-case linux-linaro-ubuntu-ip --shell ip a from: inline name: smoke-tests-basic Any ideas ? Best regards, Sebastian [View Less]

1 year, 5 months

Which kind of connection should I choose?

by liuzacharyu＠gmail.com

Hello everyone, I hava a worker in docker container, and the container runs in a Ubuntu x86 PC. now I want to make the Ubuntu x86 PC as a device and connect device to the worker run on it. Then I can execute job test actions commands in device. Which kind of connection should I choose?

1 year, 6 months

How to connect with serial port?

by irreallich＠126.com

I am newer , and I try to make new device. there is no uboot, kerner ... on my system. for boot, we just need run cmd on host "echo "reset 1" > /dev/ttyUSB0" , it is the mcu serial port. then I can get boot log from /dev/ttyUSB1 , it is thesoc serial port. the following is the job device_type: orinshort job_name: for orinshort device timeouts: job: minutes: 20 action: minutes: 15 priority: medium visibility: public actions: - deploy: timeout: minutes: 10 … [View More]

1 year, 6 months

Re: About timeouts.

by Larry Shen

Thanks Paweł Wieczorek, I'm not aware this new feature, magic job by you guys, thanks. -----Original Message----- From: lava-users-request(a)lists.lavasoftware.org <lava-users-request(a)lists.lavasoftware.org> Sent: Thursday, October 12, 2023 8:00 AM To: lava-users(a)lists.lavasoftware.org Subject: [EXT] lava-users Digest, Vol 61, Issue 10 Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report … [View More]this email' button Send lava-users mailing list submissions to lava-users(a)lists.lavasoftware.org To subscribe or unsubscribe via email, send a message with subject or body 'help' to lava-users-request(a)lists.lavasoftware.org You can reach the person managing the list at lava-users-owner(a)lists.lavasoftware.org When replying, please edit your Subject line so it is more specific than "Re: Contents of lava-users digest..." Today's Topics: 1. Re: About timeouts. (Paweł Wieczorek) ---------------------------------------------------------------------- Message: 1 Date: Wed, 11 Oct 2023 12:43:51 +0200 From: Paweł Wieczorek <pawiecz(a)collabora.com> Subject: [lava-users] Re: About timeouts. To: lava-users(a)lists.lavasoftware.org Message-ID: <32bdd741-289a-ae09-d994-f73b069a892f(a)collabora.com> Content-Type: multipart/alternative; boundary="------------4xeVji058aNHAzBX687S773k" Hi Larry, On 11.10.2023 08:04, Larry Shen wrote: > > Hi, guys, I have a question about timeout: > > 1) For next job, the boot action block's timeout will be 5 minutes, > while pdu-reboot timeout will be 10 seconds. > > timeouts: > > job: > > minutes: 10 > > action: > > minutes: 5 > > actions: > > pdu-reboot: > > seconds: 10 > > connection: > > minutes: 2 > > actions: > > - boot: > > failure_retry: 4 > > method: bootloader > > bootloader: u-boot > > commands: [] > > prompts: ['=>'] > > 2. But after we add timeouts to boot actions, the boot action timeout > is 2 minutes now, that's OK. But the individual pdu-reboot timeout > will be the left time of 2 minutes. > > actions: > > - boot: > > failure_retry: 4 > > method: bootloader > > bootloader: u-boot > > commands: [] > > prompts: ['=>'] > > timeout: > > minutes: 2 > > My question is: for the second item, if possible we could let > pdu-reboot remain the value "10 seconds"? > > Above is just an example to explain my question. What I really want to > achieve is: sometimes, I want to specify the timeout for "uboot wait > for interrupt", I want to fail that individual sub-action quickly, > then we are possible retry this action quickly without wait for the > whole boot action timeout. > You can set action block timeouts also for individual actions [0][1] - in your case it could look like: actions: - boot: failure_retry: 4 method: bootloader bootloader: u-boot commands: [] prompts: ['=>'] timeout: minutes: 2 timeouts: pdu-reboot: seconds: 10 This feature should be available if you're running LAVA 2023.01 or newer [2]. [0] https://lava.collabora.dev/static/docs/v2/actions-timeout.html#individual-a… [1] https://lava.collabora.dev/static/docs/v2/timeouts.html#action-block-overri… [2] https://gitlab.com/lava/lava/-/commit/15650f11aa10931c9b2a148ae16561b748a38… Kind regards, Paweł > Any idea? Thanks. > > Regards, > > Larry > > > _______________________________________________ > lava-users mailing list --lava-users(a)lists.lavasoftware.org > To unsubscribe send an email tolava-users-leave(a)lists.lavasoftware.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s [View Less]

1 year, 6 months

About timeouts.

by Larry Shen

Hi, guys, I have a question about timeout: 1) For next job, the boot action block's timeout will be 5 minutes, while pdu-reboot timeout will be 10 seconds. timeouts: job: minutes: 10 action: minutes: 5 actions: pdu-reboot: seconds: 10 connection: minutes: 2 actions: - boot: failure_retry: 4 method: bootloader bootloader: u-boot commands: [] prompts: ['=>'] 2. But after we add timeouts to boot actions, the boot action timeout is 2 minutes … [View More]

1 year, 6 months

How does the device run spcial cmd to build, burn and boot?

by irreallich＠126.com

Hi, There are mcu and soc on my board, two serial port for them( ttyusb0:mcu, ttyusb1:soc), the hostpc ( it is used for lava worker) connected to the two serial ports, and reboot soc cmd is echo "soc boot" > /dev/ttyUSB0 . then we can see boot log at ttyUSB1. We want to use lava to test soc system, it is arm64 with linux , without uboot . and we hope to add build action in the device. So the deploy and boot steps should be: 1. run build.sh on hostpc (it should be … [View More]lava worker) and check the result (failed and pass) 2. run echo "soc burn" > /dev/ttyUSB0 on hostpc to change the soc to burn mode, and check the result (failed and pass) 3. run burn.sh on hostpc to burn to soc , and check the result (failed and pass) 4. run echo "soc boot" > /dev/ttyUSB0 to reboot soc , and check the result (failed and pass) 5. connect to /dev/ttyUSB1 to get soc boot log, and check the result (failed and pass) 6. ssh to the linux of soc. What I want to know is: 1. Is the above design feasible on lava? 2. What do I need to do for this? Are there any device type templets that I can refer to? The following is my lava system, I can run the test job with qemu device now. ~/work/src/lava $ dpkg -l |grep lava ii lava 2022.11.1+10+buster all Linaro Automated Validation Architecture metapackage ii lava-common 2022.11.1+10+buster all Linaro Automated Validation Architecture common ii lava-coordinator 2022.11.1+10+buster all LAVA coordinator daemon ii lava-dev 2022.11.1+10+buster all Linaro Automated Validation Architecture developer support ii lava-dispatcher 2022.11.1+10+buster all Linaro Automated Validation Architecture dispatcher ii lava-dispatcher-host 2022.11.1+10+buster all LAVA dispatcher host tools ii lava-server 2022.11.1+10+buster all Linaro Automated Validation Architecture server ii lava-server-doc 2022.11.1+10+buster all Linaro Automated Validation Architecture documentation ii lava-tool 0.25-2 all deprecated command line utility for LAVA ii lavacli 0.9.7+buster all LAVA XML-RPC command line interface ~/work/src/lava $ [View Less]

1 year, 6 months

Search conditional logic in job or something else could be act as workaround.

by Larry Shen

Hi, guys, I currently have 2 jobs: Job1: actions: - boot: failure_retry: 4 method: bootloader bootloader: u-boot commands: [] prompts: ['=>'] timeout: minutes: 2 - test: timeout: minutes: 4 interactive: - name: check-uboot prompts: ["=> ", "/ # "] script: - command: "printenv" name: printenv successes: - message: "soc_type=imx93" Job2: actions: - deploy: to : uuu images : boot : … [View More]

1 year, 6 months

is https://docs.lavasoftware.org server for LAVA document not supported anymore?

by 김서지 Lily

Hi. Is https://docs.lavasoftware.org server for LAVA document not supported anymore? I can't access the site anymore. Thank you.

1 year, 6 months

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users