lava-users April 2022

lava-users@lists.lavasoftware.org

5 participants
6 discussions

by Milosz Wasilewski

Hi, I'm trying to test HDMI output from my DUT. The HDMI-USB capture device is plugged to the dispatcher. The test is simple: it captures a frame from the video device on the dispatcher and compares it to the reference. If the difference is below threshold, the test is passed. Is there an easy way of running such a test without starting all multi-node + docker machinery? Best Regards, Milosz

2 years, 12 months

How to retrieve the prompt content with Uboot

by Roselyne MAZIERES

Hello, We are writing an interactive test for uboot. Here is the command we send: timer start && nand read \${TMPADDR} ${nand_offset} \${TMPSIZE} && timer get || run fail And below is what we get. In the traces, after the "524288 bytes read: OK", there is the timer info: 0.080. We need to be able to catch this value and we need to perform computation on it and some comparison afterwards. Do you have a solution to do that? What would you advise us to do? Thanks a lot for your help! Best regards, Roselyne Mazières [cid:image001.png@01D8390F.5506EEC0] Internal

3 years

need fix for "shutdown-message" support

by koti

Hi, My test job .yaml does not provide any error while health-check trigger from GUI and give error while submitting the same test job from the command line . you can find the command line submission error as mentioned below. " lavamaster@lava$lavacli -i admin@validation jobs submit /tmp/test.yaml Unable to submit /tmp/target.yaml: <Fault 400: "Problem with submitted job data: expected str for dictionary value @ data['actions'][0]['boot']['parameters']['shutdown-message']">" " I have reported same type of bug for "soft-reboot" command support and provided the patch by lava-team for this soft-reboot support issue i.e " https://git.lavasoftware.org/lava/lava/-/merge_requests/1067/diffs#05da71b3… " Can someone provide the path for "shutdown-message" support also? Regards, Koti

3 years

Unable to delete Lava devices

by DAS, BHARGAV

Hi Lava Users, We are facing issue while deleting/removing some devices from LAVA. After clicking the "Delete" button located in "http://<lava url>/admin/lava_scheduler_app/device/<device we want to remove>/change/<http://%3clava%20url%3e/admin/lava_scheduler_app/device/%3cdevice%20we%20want%20to%20remove%3e/change/>" the following message is observed "Proxy Error" (check the attached image for the complete message) This error is observed only in some devices. The worker of the device is offline and in maintenance state. Regards, Bhargav

3 years

lava-wait stuck in loop with multinode protocol

by abhilash.ramineni＠nxp.com

with multinode protocol device is not able to proceed from lava-wait sometimes, even though other device has sent lava-send message

3 years

HTTPS configuration for LAVA Server.

by K L, Shivaschandra (DI SW CAS ES EPT OPS&QA PBU)

Hi All , We had lava-server running on HTTP , we needed to migrate to HTTPS for security reasons. We have configured our lava-server for HTTPS by configuring apache2 with root and issuing SSL certificates. Post migration from HTTP to HTTPS, lava server works fine , but we are facing issues while worker tries to connect to lava server, Following is the error that we are getting in lava-worker.log ERROR -> server error: code 503 2022-03-29 19:38:15,598 DEBUG --> HTTPSConnectionPool(host='*.com', port=443): Max retries exceeded with url: /scheduler/internal/v1/workers/<worker-name> /?version=2021.10 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1123)'))) Are there any configurations that we have to do on the worker side to enable the sever - worker communication to be up and running. If there are any documentations that need to be followed to configure HTTPS , request to provide the documentation for the same. Thanks and regards Shivaschandra K L

3 years

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users April 2022