- lava-users - op-lists.linaro.org

by Paul Spooren

Hi, I’m tying to login to git.lavasoftware.org but neither is my account approved nor does GitHub logins work (500 error). Could someone please unlock my account or fix the GitHub issue? Thanks! Paul

2 years, 8 months

1
0
0 0

Using SCP to deploy overlayfs

by Paul Spooren

Hi all, I’m failing to understand how to transfer an overlay (containing tests) to an embedded device. My device health check runs a Kernel via tftp and works fine. When I’m trying to add tests it fails since the overlay isn’t found. How are tests added when outside of a QEMU instance (which uses mount)?. My idea was to use SCP but defining a `ssh_host` for for the targeted device gives me an error since power commands are defined. I’m thinking of a workflow like tftpboot -> wait for prompt -> run scp -> run tests. All I could find in the docs is MultiNode related, which is from my understanding something I don’t want for this very basic testing. Could someone please give me some advise? Best, Paul

2 years, 9 months

2
2
0 0

Running dispatcher/worker on OpenWrt

by Paul Spooren

Hi all, I’m planing to test some boards running OpenWrt. Since I have plenty of routers capable to run Python code I’m wondering if someone managed to run a dispatcher/worker outside of Debian? About 7 years ago people seem to have managed that[1] but the code base changed quite a bit, I figured. Thanks for all further advice! Best, Paul [1]: https://gitlab.nic.cz/turris/openwrt-lava/-/blob/master/lava-dispatcher/Mak…

2 years, 9 months

2
2
0 0

Console connection terminates , if target physical reset with "pdu""

by koti

Hi, My console connection terminates if I add the logic to reset my target physically. But this does not if I reboot my target using "reboot" I suspect this issue may arise due to re-initiating my target USB-Serial ftdi driver after target physical power off/on. Is there any way to re-establish the terminal connection after physically rebooting my target without terminating? Attached screenshots. Regards, Koti

2 years, 9 months

1
0
0 0

"email" notification feature info

by koti

Hi, I just want to know if there is any "email" notification facility in our lava test framework. Example: ######## 1. We need to recevied below notification to configured email id a. Test trigger info b. Test complete/canceled/incomplete info Regards, Koti

2 years, 10 months

2
2
0 0

Re: [EXT] Device stuck in 'Running'

by Larry Shen

I met this for twice during past years, I use django shell to reset the state, FYI: sudo lava-server manage shell from lava_scheduler_app.models import Device Device.objects.filter(hostname="imx8mm-evk-sh99").update(state=Device.STATE_IDLE) -----Original Message----- From: lava-users-request(a)lists.lavasoftware.org <lava-users-request(a)lists.lavasoftware.org> Sent: Tuesday, June 7, 2022 8:00 AM To: lava-users(a)lists.lavasoftware.org Subject: [EXT] Lava-users Digest, Vol 46, Issue 3 Caution: EXT Email 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: [EXTERNAL] Re: Device stuck in 'Running' (Milosz Wasilewski) ---------------------------------------------------------------------- Message: 1 Date: Mon, 6 Jun 2022 13:39:08 +0100 From: Milosz Wasilewski <milosz.wasilewski(a)foundries.io> Subject: [Lava-users] Re: [EXTERNAL] Re: Device stuck in 'Running' To: "Westermann, Oliver" <Oliver.Westermann(a)cognex.com> Cc: "lava-users(a)lists.lavasoftware.org" <lava-users(a)lists.lavasoftware.org> Message-ID: <CAH1=h_QrLjTp5g+gCgVnZ1fyi+M7tnamAqEngzxjCj--H+2wAw(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" On Thu, Jun 2, 2022 at 10:36 AM Westermann, Oliver <Oliver.Westermann(a)cognex.com> wrote: > > Hey, > > > From: Milosz Wasilewski <milosz.wasilewski(a)foundries.io> > > > > On Tue, May 31, 2022 at 9:04 PM Westermann, Oliver <Oliver.Westermann(a)cognex.com> wrote: > > > > > > Hey, > > > > > > I've a device stuck in 'Running' state, but missing the usual appending of '#<123> <Job Name> [submitter]'. > > > > > > Does somebody have some tips how to set/force the device state to 'Idle' manually? > > > > I put my bet on lava-dispatcher crashing somewhere along the way. > > Please try to restart lava-dispatcher and all services around it (webserver, ser2net, etc.). > > Did so before my mail request. We're running the docker-compose setup and I've already update (to 2022.05) and restarted (and rebuild) the containers with no success. That's weird. It should fix the issue > > > Once you've done this, you can mark the device "idle" in the admin interface. This should help. > > Can you give me some guidance here? The admin interface (as well as the lava-server cli) allow me to set the health (good, bad, maintenance, retired), but not the state. My bad, you're absolutely right. The state field doesn't seem to be editable. You might need to change it in the DB. I've no idea how it got to this point. In my case when dispatcher is restarted the device status usually fixes itself. One thing to consider is deleting the offending TestJob from DB. This might help (I didn't look at the code to confirm it) > > Unrelated sidenote: > Rebuilding the docker containers failed me. > The dispatcher requires a file from schneider electric [1], which is currently not available for me. > I found the file on Remis Github [2] and fixed my Dockerfile locally, but I will try to create a Issue in the gitlab. It's MIB for APC PDU (or some other Schneider equipment). It's only required if you're using SNMP to talk to PDU with the name instead of it's ASN.1 number. Linaro's lab-scripts [1] make use of this MIB. [1] https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.linar… Best Regards, Milosz > > Best regards, Olli > > [1] > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit. > lavasoftware.org%2Flava%2Fpkg%2Fdocker-compose%2F-%2Fblob%2Fmaster%2Fd > ispatcher%2FDockerfile%23L14&data=05%7C01%7Clarry.shen%40nxp.com%7 > Ce553a3e81ed4483b0aa508da4818b237%7C686ea1d3bc2b4c6fa92cd99c5c301635%7 > C0%7C0%7C637901568148410870%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMD > AiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&s > data=jQS9w3MoZmp5zq6GwQHleYhWuYRUOAyIEB7mVTPVIvc%3D&reserved=0 > [2] > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith > ub.com%2Fci-box%2Fci-box-lava-worker%2Fblob%2Fmaster%2Fpowernet428.mib > &data=05%7C01%7Clarry.shen%40nxp.com%7Ce553a3e81ed4483b0aa508da481 > 8b237%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637901568148410870% > 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik > 1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oQ%2B4ZVu7i27IA4%2BHBD3 > mzToa4nLUurFPSP4VoFyojU0%3D&reserved=0 > ------------------------------ Subject: Digest Footer _______________________________________________ Lava-users mailing list -- lava-users(a)lists.lavasoftware.org To unsubscribe send an email to lava-users-leave(a)lists.lavasoftware.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s ------------------------------ End of Lava-users Digest, Vol 46, Issue 3 *****************************************

2 years, 11 months

1
0
0 0

Device stuck in 'Running'

by Westermann, Oliver

Hey, I've a device stuck in 'Running' state, but missing the usual appending of '#<123> <Job Name> [submitter]'. It does not accept new jobs and cycling it through it's health states does not change the state. We had to reboot our systems unplanned (and uncoordinated) today, so that might be the cause of the issue, but I would like to get my device back :D Google surfaced an old, outdated FAQ in the lava sources [1], and a bug marked as solved in our version 2021.11 [2], but both didn't really don't work as expected. Does somebody have some tips how to set/force the device state to 'Idle' manually? Best regards, Olli [1] https://git.lavasoftware.org/balikm/lava/-/blob/2015.01/doc/faq.rst [2] https://git.lavasoftware.org/lava/lava/-/issues/471

2 years, 11 months

2
3
0 0

Advice on Job definition in lava:

by pawanKumar

Hello Team, Good Day to you! I'm new to the Lava Environment and need advice on writing a job definition to run a script which can perform booting, run the tests and report results. I don't need to deploy and boot. Below is the job def. I'm trying to work. Please suggest any changes I should make. device_type: x86 job_name: Execute the script timeouts: job: minutes: 20 action: minutes: 20 connection: minutes: 5 visibility: public actions: - test: timeout: minutes: 10 definitions: - repository: metadata: format: Lava-Test Test Definition name: testing description: "Sanity Test on Beaglebone" os: - Linux scope: - functional run: steps: - "cd Folder_name/" - "./test_script.sh" Thanks.

2 years, 12 months

1
0
0 0

Running a test on dispatcher

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

3 years

2
2
0 0

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, 1 month

2
2
0 0

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, 1 month

2
6
0 0

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, 1 month

2
5
0 0

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, 1 month

2
1
0 0

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, 1 month

2
2
0 0

LAVA bug when trying to use case sensitive file names with flasher

by Milosz Wasilewski

Hi, I'm trying to use flashing script with one of my IMX family boards. Flashing one of the boards requires a file which name starts with SPL-. I need to pre-process some of the downloaded files so I'm using deploy-to-downloads. After that I'm using deploy-to-flasher to flash the board with NXP's uuu tool. Unfortunately copying files from deploy-to-downloads to deploy-to-flasher results in losing the uppercase characters. This is due to LAVA internally using urllib.parse.urlparse.hostname. This method always returns lowercase strings. This doesn't matter in case of http(s) URLs but makes a difference in LAVA's internal download:// URLs. To fix that, 'hostname' should be changed to 'netloc'. I sent the patch to my branch here: https://git.lavasoftware.org/mwasilew/lava/-/tree/downloads-url-case Unfortunately I'm no longer able to create a merge request (sth wrong with authentication in gitlab). Could someone with enough powers pull this patch? Best Regards, Milosz

3 years, 2 months

2
2
0 0

Re: Job is not exiting after the timeout

by P T, Sarath

Hi Team, I could able to find the root cause of the issue just giving my observation : 1. I deleted a `cancelling` job with the ID 3834 from the GUI. 2. And for the next test run its giving an error log under worker like this . 2022-02-24 01:18:57,502 ERROR [3834] -> server error: code 503 2022-02-24 01:18:57,502 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-24 01:19:16,795 INFO PING => server 2022-02-24 01:19:17,268 INFO [3834] FINISHED => server 2022-02-24 01:19:18,666 ERROR [3834] -> server error: code 404 2022-02-24 01:19:18,666 DEBUG [3834] --> {"error": "Unknown job '3834'"} 2022-02-24 01:19:36,797 INFO PING => server 2022-02-24 01:19:37,274 INFO [3834] FINISHED => server 2022-02-24 01:19:37,509 ERROR [3834] -> server error: code 503 2022-02-24 01:19:37,509 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) So can you people help me what this behaviour is for and a solution too ? Your response will be a great help for me. Regards Sarath P T From: P T, Sarath Sent: 23 February 2022 14:26 To: lava-users(a)lists.lavasoftware.org Subject: Job is not exiting after the timeout Hi Team, Facing an issue related to the LAVA job timeout. Job is not exiting even after the timeout , its continuously loading after the job completion. Below I am giving my observations: 1. A LAVA job has executed with the job id : 3959 2. And under the worker I am getting the log as shown below : 2022-02-22 23:19:09,534 DEBUG [3959] dispatch: None 2022-02-22 23:19:09,535 DEBUG [3959] env : {'purge': True, 'overrides': {'LC_ALL': 'C.UTF-8', 'LANG': 'C', 'PATH': '/usr/local/bin:/usr/local/sbin:/bin:/usr/bin:/usr/sbin:/sbin'}} 2022-02-22 23:19:09,535 DEBUG [3959] env-dut : None 2022-02-22 23:19:09,584 INFO [3959] RUNNING => server 2022-02-22 23:19:09,850 INFO [3834] FINISHED => server 2022-02-22 23:19:10,087 ERROR [3834] -> server error: code 503 2022-02-22 23:19:10,088 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:19:28,651 INFO PING => server 2022-02-22 23:19:29,142 INFO [3834] FINISHED => server 2022-02-22 23:19:29,775 ERROR [3834] -> server error: code 503 2022-02-22 23:19:29,776 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:19:48,652 INFO PING => server 2022-02-22 23:19:49,146 INFO [3834] FINISHED => server 2022-02-22 23:19:49,391 ERROR [3834] -> server error: code 503 2022-02-22 23:19:49,391 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:20:08,653 INFO PING => server 2022-02-22 23:20:09,171 INFO [3959] running -> finished 2022-02-22 23:20:09,224 INFO [3834] FINISHED => server 2022-02-22 23:20:09,525 ERROR [3834] -> server error: code 503 2022-02-22 23:20:09,525 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:20:28,654 INFO PING => server 2022-02-22 23:20:29,147 INFO [3834] FINISHED => server 2022-02-22 23:20:29,756 ERROR [3834] -> server error: code 503 2022-02-22 23:20:29,756 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) Seems after the job execution somewhere the communication between server and worker is getting interrupted. It will be a great help if you people are looking into the issue and hope you will find the solution for the same. Regards Sarath P T

3 years, 2 months

2
3
0 0

LAVA Dispatcher on Raspberry Pi OS (64 bit)

by Colin Thorbinson

Hi All, We are planning on deploying some Raspberry Pi's as LAVA dispatchers in our lab. Does LAVA fully support Raspberry Pi OS and are there any known limitations we should be aware of? Many thanks, Colin 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.

3 years, 2 months

2
1
0 0

Job is not exiting after the timeout

by P T, Sarath

Hi Team, Facing an issue related to the LAVA job timeout. Job is not exiting even after the timeout , its continuously loading after the job completion. Below I am giving my observations: 1. A LAVA job has executed with the job id : 3959 2. And under the worker I am getting the log as shown below : 2022-02-22 23:19:09,534 DEBUG [3959] dispatch: None 2022-02-22 23:19:09,535 DEBUG [3959] env : {'purge': True, 'overrides': {'LC_ALL': 'C.UTF-8', 'LANG': 'C', 'PATH': '/usr/local/bin:/usr/local/sbin:/bin:/usr/bin:/usr/sbin:/sbin'}} 2022-02-22 23:19:09,535 DEBUG [3959] env-dut : None 2022-02-22 23:19:09,584 INFO [3959] RUNNING => server 2022-02-22 23:19:09,850 INFO [3834] FINISHED => server 2022-02-22 23:19:10,087 ERROR [3834] -> server error: code 503 2022-02-22 23:19:10,088 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:19:28,651 INFO PING => server 2022-02-22 23:19:29,142 INFO [3834] FINISHED => server 2022-02-22 23:19:29,775 ERROR [3834] -> server error: code 503 2022-02-22 23:19:29,776 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:19:48,652 INFO PING => server 2022-02-22 23:19:49,146 INFO [3834] FINISHED => server 2022-02-22 23:19:49,391 ERROR [3834] -> server error: code 503 2022-02-22 23:19:49,391 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:20:08,653 INFO PING => server 2022-02-22 23:20:09,171 INFO [3959] running -> finished 2022-02-22 23:20:09,224 INFO [3834] FINISHED => server 2022-02-22 23:20:09,525 ERROR [3834] -> server error: code 503 2022-02-22 23:20:09,525 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) 2022-02-22 23:20:28,654 INFO PING => server 2022-02-22 23:20:29,147 INFO [3834] FINISHED => server 2022-02-22 23:20:29,756 ERROR [3834] -> server error: code 503 2022-02-22 23:20:29,756 DEBUG [3834] --> ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response')) Seems after the job execution somewhere the communication between server and worker is getting interrupted. It will be a great help if you people are looking into the issue and hope you will find the solution for the same. Regards Sarath P T

3 years, 2 months

2
1
0 0

Lava JOB status still shows running even after job completed

by koti

Hi, My LAVA job status still shows "Running" even when the job is completed and status does not change even after 24 hours. Due to that my other Job's pending from that dispatcher targets. My dispatcher shows these errors for /var/log/lava-dispatcher/lava-worker.log i.e " https://pastebin.com/46WFtAin" Please can someone let me know a solution to fix this issue? Regards, Koti

3 years, 2 months

2
2
0 0

Flashrom

by koti

Hi Cano Pablo, If my understanding is correct, you may want to flash the images in boot action. We can flash the same using the below boot action. " actions: - deploy: timeout: minutes: 10 to: flasher images: image: url: file: <firmware path> - boot: method: bootloader bootloader: u-boot commands: - ' xxxxx' prompts: - 'xxxxx' timeout: minutes: 10 " 1. Please provide your flash script under /etc/lava-server/dispatcher-config/devices/<device.jinja2> file as mentioned below under "flasher_deploy_commands" Example: (Note: {IMAGE} is the file mentioned in Deply action i.e "url: file: <firmware path>" {% set flasher_deploy_commands = ['/1.py', 'sleep 10', '/2.py', 'sleep 10', '/flash.sh "{IMAGE}" &', 'sleep 2', 'sleep 2'] %} 2. Please mention your bootmethod and bootloader as per your requirement. Regards, Koti On Wed, 2 Feb 2022 at 05:30, <lava-users-request(a)lists.lavasoftware.org> wrote: > 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. Flashrom (Cano, Pablo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 1 Feb 2022 23:21:42 +0000 > From: "Cano, Pablo" <Pablo.Cano(a)Resideo.com> > Subject: [Lava-users] Flashrom > To: "lava-users(a)lists.lavasoftware.org" > <lava-users(a)lists.lavasoftware.org> > Message-ID: <SN4PR22MB33174DEF13E85267D949A52B8B269(a)SN4PR22MB3317.nam > prd22.prod.outlook.com> > Content-Type: multipart/alternative; boundary="_000_SN4PR22MB33174D > EF13E85267D949A52B8B269SN4PR22MB3317namp_" > > Hi, > Someone knows how to implement flashrom in the booting action of the > device type? >

3 years, 3 months

1
0
0 0

Flashrom

by Cano, Pablo

Hi, Someone knows how to implement flashrom in the booting action of the device type?

3 years, 3 months

1
0
0 0

Add new device TI CC1312

by Cano, Pablo

Hi, I'm starting to work with LAVA and I want to know if there is a template for a Texas Instrument microcontroller like CC1312. Also, I want to know if someone try to connect a DUT with CHEETAH that is a SPI host adapter. If so, what is the method to communicate it with LAVA? Best, Pablo

3 years, 3 months

1
0
0 0

Re: [Lava-users] Add new device NXP rt1050

by Philippe Mazet (OSS)

The IMXRT1050 seems to be already supported, including jlink support. https://git.lavasoftware.or/lava/lava/-/blob/master/etc/dispatcher-config/d… And since the device-type template already exists in LAVA, it should not be too complicated to get started with it. However, I am not using this type of device myself, so I can't help more. Philippe From: Lava-users <lava-users-bounces(a)lists.lavasoftware.org> On Behalf Of Cano, Pablo Sent: Friday, January 21, 2022 10:36 PM To: lava-users(a)lists.lavasoftware.org Subject: [Lava-users] Add new device NXP rt1050 Hi, I'm starting to work with LAVA and I read the documentation about add a new device is more difficult rather than use some templates. So, my question is if there is a template to use with a microprocessor like rt1050 that has an architecture ARM7vE-M. Also, I need to communicate to this unit with J-link and UART, is possible to use direct communication or I need to connect via the network.

3 years, 3 months

1
0
0 0

Add new device NXP rt1050

by Cano, Pablo

Hi, I'm starting to work with LAVA and I read the documentation about add a new device is more difficult rather than use some templates. So, my question is if there is a template to use with a microprocessor like rt1050 that has an architecture ARM7vE-M. Also, I need to communicate to this unit with J-link and UART, is possible to use direct communication or I need to connect via the network.

3 years, 3 months

1
0
0 0

how to edit the configured "lava-worker" host name

by koti

Hi, Recently my "lava-worker" host name was changed and showed the same offline in Lava-server. Is there any easy way to edit the old hostname with the new hostname (in lava-server side software) to bring back the lava-worker/dispatcher online ? Regards, Koti

3 years, 4 months

1
0
0 0

How to install 2021.10 "Lava-dispatcher" now

by koti

Hi, I plan to install the 2021.10 lava-dispatcher instead of the 2021.11 latest version. I am unable to install the 2021.10 lava-dispatcher version but able to install 2021.11 using "apt install lava-dispatcher" Is there any way to install the 2021.10 lava-dispatcher at this time? Or do we always need to install the latest versions? Regards, koti

3 years, 4 months

3
3
0 0

Re: [Lava-users] Lava-users Digest, Vol 39, Issue 11

by koti

Hi Nagerndra, I would recommend send a patch if the issue is resolved so that the LAVA team will review/check it. Regards, Koti On Thu, 25 Nov 2021 at 17:30, <lava-users-request(a)lists.lavasoftware.org> wrote: > Send Lava-users mailing list submissions to > lava-users(a)lists.lavasoftware.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.lavasoftware.org/mailman/listinfo/lava-users > or, 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: Constant failure_retry does not exist in the device > config 'constants' (Nagendra Singamsetti) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 24 Nov 2021 18:02:59 +0530 > From: Nagendra Singamsetti <nag.singam91(a)gmail.com> > To: lava-users(a)lists.lavasoftware.org > Subject: Re: [Lava-users] Constant failure_retry does not exist in the > device config 'constants' > Message-ID: > <CAFhg_Wtt3+AnYRLLO7nm2u8uiYKLFPHaS7_Q5LKvah= > 0Z_vsSg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi All , > The Issue got solved by updating the latest change in base.jinja2 > device-type file. > > # Set the failure retry to default or override it failure_retry: {{ > failure_retry|default(1) }} # Override boot_retry boot_retry: {{ > boot_retry }}{% endblock constants -%} > > I am not sure why base.jinja2 is not updated during the 2021.10 > lava-server upgrade process. If any one got the same issue please try > this change. > > thanks > > Regards > > Nagendra S > > > On Wed, Nov 24, 2021 at 1:19 PM Nagendra Singamsetti < > nag.singam91(a)gmail.com> > wrote: > > > Hi All, > > > > I got struck with strange issue with latest version 2021.10 > > > > > > - *error_msg*: Constant failure_retry does not exist in the device > > config 'constants' section. > > - *error_type*: Configuration > > > > ConfigurationError: The LAVA instance is not configured correctly. Please > > report this error to LAVA admins. > > > > My setup is working fine with 2021.05. But after upgrading with the > latest > > version 2021.10 none of the jobs are not working. Always it raises the > > Exception called Configuration Error. > > > > Looking forward to your kind response!!! > > > > > > Regards > > Nagendra S > > > > > > >

3 years, 5 months

1
0
0 0

Constant failure_retry does not exist in the device config 'constants'

by Nagendra Singamsetti

Hi All, I got struck with strange issue with latest version 2021.10 - *error_msg*: Constant failure_retry does not exist in the device config 'constants' section. - *error_type*: Configuration ConfigurationError: The LAVA instance is not configured correctly. Please report this error to LAVA admins. My setup is working fine with 2021.05. But after upgrading with the latest version 2021.10 none of the jobs are not working. Always it raises the Exception called Configuration Error. Looking forward to your kind response!!! Regards Nagendra S

3 years, 5 months

1
1
0 0

API PUT call permissions

by Milosz Wasilewski

Hi, I'm running a project which requires changes in device status in LAVA. It will request the device to be put into 'maintenance' and later on into 'good' state. Initially I was using my personal API token. Since I was a superuser it all worked. A few weeks ago I tried to move to a more permanent solution with a dedicated user. I granted all required access rights to the new user, but PUT calls to api/v0.2/devices/<device_name> were rejected. After looking at the code it seems that only superuser is allowed to make such calls. Is there a reason for that? Changes were introduced in this commit: https://git.lavasoftware.org/lava/lava/-/commit/2bdbd462d745b45308faf86dd37… Best Regards, Milosz

3 years, 5 months

2
2
0 0

using 'uuu' boot action results in KeyError: 'uuu' on v2021.09

by Davis Roman

Hello, I received an error message when using the 'uuu' boot action on v2021.09. I tried poking around through the lava source but I'm still fairly new to the repo so I'm a bit stumped. Any comments or suggestions would be greatly appreciated. Thank you, Davis Traceback (most recent call last): File "/bin/lava-run", line 240, in main job = parse_job_file(logger, options) File "/bin/lava-run", line 151, in parse_job_file env_dut=env_dut, File "/usr/lib/python3/dist-packages/lava_dispatcher/parser.py", line 163, in parse test_counts[namespace], File "/usr/lib/python3/dist-packages/lava_dispatcher/parser.py", line 47, in parse_action cls = Boot.select(device, parameters) File "/usr/lib/python3/dist-packages/lava_dispatcher/logical.py", line 276, in select res = c.accepts(device, parameters) File "/usr/lib/python3/dist-packages/lava_dispatcher/actions/boot/uuu.py", line 119, in accepts params = device["actions"]["boot"]["methods"]["uuu"]["options"] KeyError: 'uuu' LAVABug: This is probably a bug in LAVA, please report it. --------------------------------------------------------------------------------------------------------------------------- device_type: imx8m job_name: flash with uuu timeouts: job: minutes: 10 action: minutes: 10 connection: minutes: 5 visibility: public actions: - deploy: to: uuu images: boot: url: file:///home/davis/uuu/imx-boot-64.bin system : url: file:///home/davis/uuu/sd.img - boot: method: uuu commands : - uuu: -b emmc_all {boot} {system}

3 years, 6 months

4
8
0 0

dispatcher docker image overwrites ENV

by Benedikt Braunger

Moin, I'm using https://git.lavasoftware.org/lava/pkg/docker-compose to build example setups with LAVA and I want to add a second remote worker. Therefore I set the URL and DC_DISPATCHER_HOSTNAME in .env and run `docker-compose up lava-dispatcher`. Sadly the dispatcher always tries to connect to "lava-server" dispite that the correct URL is passed via environment variables into the container. It looks like the value gets overwritten in https://git.lavasoftware.org/lava/lava/-/blob/master/docker/share/entrypoin… as the lava-worker file looks like this inside the container. ... # Logging level should be uppercase (DEBUG, INFO, WARN, ERROR) # LOGLEVEL="DEBUG" # Server connection URL="http://lava-server:8000/" # TOKEN="--token <token>" WS_URL="--ws-url http://lava-publisher:8001/ws/" After digging around a bit I found out, that this environment file comes from https://git.lavasoftware.org/lava/pkg/docker-compose/-/blob/master/overlays… This practically disables the possibility of configuring the worker via the .env of the docker-compose repo. The order of defaults loading in https://git.lavasoftware.org/lava/lava/-/blob/master/docker/share/entrypoin… should be changed, so that the importing from the lava-worker file happens first and the environment variable is applied afterwards. Overall there are two defaults here and two possibilities to configure the worker, which is a bit confusing and redundant. Imho the .env from the docker-compose repo is a known and established way of configuring containers and should be preferred. Regards, Beni -- Benedikt Braunger emlix GmbH, http://www.emlix.com Fon +49 551 30664-0, Fax +49 551 30664-11 Gothaer Platz 3, 37083 Goettingen, Germany Sitz der Gesellschaft: Goettingen, Amtsgericht Goettingen HR B 3160 Geschaeftsfuehrung: Heike Jordan, Dr. Uwe Kracke Ust-IdNr.: DE 205 198 055 emlix - smart embedded open source

3 years, 6 months

1
0
0 0

Parsing test result that include square brackets in interactive test

by 김서지

3 years, 6 months

1
0
0 0

All device become 'Bad (Invalid device configuration)' after lava server re-install

by Kever Yang

Hi I setup a LAVA server few years ago, on Debian 9.5 Stretch(with Python 3.5), and it works correctly. Recently I update the Python to 3.6, but the lava-server not able to work correctly. eg. the HTTP server does not work. So I fall back to Python 3.5 and re-install the LAVA server at the same time, but unfortunately the device does not work this time. The device status is set to "Bad (Invalid device configuration)" by the lava-health without any real check. The device was work correctly, and only change to 'BAD' when health check job get fail. Is there any device related option was set to mandatory instead of optional which cause this issue? How can I identify this issue? I can't see any Error in the log file at /var/log/lava-server Thanks, - Kever

3 years, 6 months

1
1
0 0

Can't I use ']' on bootloader_prompt and "$'\cc'" on interrupt_char?

by 김서지

3 years, 6 months

1
0
0 0

How to write dummy deploy action to test already flashed and booted DUT?

by 김서지

3 years, 7 months

1
0
0 0

Re: [Lava-users] Email notifications broken in LAVA 2021.08

by Westermann, Oliver

> I actually didn?t upgrade anything myself: I am using your > docker-compose solution, on a Ubuntu 18.04 host. Just as a sidenote as I noticed this as well: We also use the docker-compose setup and while I did not investigate the reasons yet, I can confirm that our mailed notifications are broken since the recent update. I didn't care to much as we check manually either way, but I can confirm from my last e-mail that the "breaking change" was simply a rebuild of the docker compose setup with the latest updates, but no host changes. - Olli

3 years, 7 months

1
0
0 0

Re: [Lava-users] Email notifications broken in LAVA 2021.08 ?

by Remi Duraffort

Hello, Le lun. 27 sept. 2021 à 17:14, Philippe Mazet (OSS) < philippe.mazet(a)oss.nxp.com> a écrit : > I actually didn’t upgrade anything myself: I am using your docker-compose > solution, on a Ubuntu 18.04 host. > > But your image in dockerhub (lavasoftware/lava-server:2021.08) upgraded to > bullseye, yes. > Have you tried creating your own derivative of the lavasoftware/lava-server:2021.08 image and installing eventlet from pypi? Rgds > > > Thanks, > > > > Philippe > > > > > > *From:* Lava-users <lava-users-bounces(a)lists.lavasoftware.org> *On Behalf > Of *Remi Duraffort > *Sent:* Monday, September 27, 2021 5:05 PM > *To:* Philippe Mazet (OSS) <philippe.mazet(a)oss.nxp.com> > *Cc:* lava-users(a)lists.lavasoftware.org <lava-users(a)lavasoftware.org> > *Subject:* Re: [Lava-users] Email notifications broken in LAVA 2021.08 ? > > > > Hello, > > > > > > Le jeu. 23 sept. 2021 à 13:54, Philippe Mazet (OSS) < > philippe.mazet(a)oss.nxp.com> a écrit : > > Hi All, > > > > We are hitting a bug with LAVA 2021.08: email notifications seem to be > broken. > > We believe this is due to a bug between eventlet 0.26.0 and dnspython. > > Visibly, this is fixed in eventlet 0.32.0: > https://github.com/eventlet/eventlet/issues/619 > > > > Did you face the same bug? > > > > I guess you upgraded to bullseye? Because LAVA 2021.08 hasn't changed > anything regarding it's requirements. > > > > > > Any idea about how to fix that? > > > > Depending on which debian version you are using. Either ask a DD to upload > python-eventlet 0.32 and to upload it to bullseye-backports. > > > > > > > > Thanks a lot, > > > > Philippe > > > > Trace below: > > ERROR:lava_scheduler_app:[Errno -3] Lookup timed out > > Traceback (most recent call last): > > File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line > 435, in resolve > > return _proxy.query(name, rdtype, raise_on_no_answer=raises, > > File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line > 391, in query > > return end() > > File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line > 370, in end > > raise result[1] > > File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line > 351, in step > > a = fun(*args, **kwargs) > > File "/usr/lib/python3/dist-packages/dns/resolver.py", line 1089, in > query > > return self.resolve(qname, rdtype, rdclass, tcp, source, > > File "/usr/lib/python3/dist-packages/dns/resolver.py", line 1043, in > resolve > > timeout = self._compute_timeout(start, lifetime) > > File "/usr/lib/python3/dist-packages/dns/resolver.py", line 950, in > _compute_timeout > > raise Timeout(timeout=duration) > > dns.exception.Timeout: The DNS operation timed out after 5.104917526245117 > seconds > > _______________________________________________ > Lava-users mailing list > Lava-users(a)lists.lavasoftware.org > https://lists.lavasoftware.org/mailman/listinfo/lava-users > > > > > -- > > Rémi Duraffort > > TuxArchitect > > Linaro > -- Rémi Duraffort TuxArchitect Linaro

3 years, 7 months

1
0
0 0

two boot actions in single job

by Milosz Wasilewski

Hi, I'm trying to run a job which reboots the board. The reboot is controlled with interactive shell. After issuing 'reboot' I try to run a 'boot' action with download overlay. This unfortunately fails. If there is 'transfer_overlay' lava complains there is no overlay available to download. When I remove 'transfer_overlay' lava complains there are no tests to run. I guess I need to add 'deploy' action before the second boot, but I don't know how to do it properly. The DUT should be left on it's own and not reflashed. Here is my job definition: actions: - deploy: namespace: before timeout: minutes: 10 to: flasher images: image: .... - boot: namespace: before prompts: - "root@imx8mmevk" timeout: minutes: 10 auto_login: login_prompt: 'login:' username: fio password_prompt: "Password:" password: "fio" login_commands: - sudo su - fio method: minimal transfer_overlay: download_command: cd /home ; wget unpack_command: tar -C / -xzf - test: namespace: before timeout: minutes: 5 definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: prepare-upgrade description: "OTA upgrade" os: - debian scope: - functional run: steps: ... from: inline name: prepare-upgrade path: inline/prepare-upgrade.yaml - test: namespace: before timeout: minutes: 1 interactive: - name: reboot prompts: ['root@imx8mmevk',] script: - command: reboot name: reboot - boot: namespace: after connection-namespace: before prompts: - "root@imx8mmevk" timeout: minutes: 10 auto_login: login_prompt: 'login:' username: fio password_prompt: "Password:" password: "fio" login_commands: - sudo su - fio method: minimal transfer_overlay: download_command: cd /home ; wget unpack_command: tar -C / -xzf - test: namespace: after connection-namespace: before timeout: minutes: 5 definitions: - repository: metadata: format: Lava-Test Test Definition 1.0 name: verify-rollback description: "OTA upgrade" os: - debian scope: - functional run: steps: ... from: inline name: verify-rollback path: inline/verify-rollback.yaml I removed the test steps as they're not relevant. The 'before' and 'after' namespaces are required. Without namespaces LAVA will only run last boot and test sections and ignores the ones in 'before' namespace. To conclude - does anyone know how to make this job working? Either by adding a 'dummy deploy' to the 'after' namespace or by getting rid of namespaces so all tests are executed in the defined order? Best Regards, Milosz

3 years, 7 months

2
2
0 0

Kernel message during LAVA signal breaks database

by Westermann, Oliver

Hey, Yesterday a kernel message was printed during a LAVA Signal. Lava therefore got a test named '0-mytest-cutoff[', the [ being the beginning of the timestamp of a kernel message. Afterwards several web views like the result overview were broken due to some filter not being able to deal with '0-mytest-cutoff['. We fixed this by taking lava offline and doing a search&replace on the database to rename the test. It seems to be the default to have the full kernel log on the LAVA serial output. Is this an expected behaviour and is there a good way to prevent those issues? Best regards, Olli

3 years, 7 months

2
1
0 0

Email notifications broken in LAVA 2021.08 ?

by Philippe Mazet (OSS)

Hi All, We are hitting a bug with LAVA 2021.08: email notifications seem to be broken. We believe this is due to a bug between eventlet 0.26.0 and dnspython. Visibly, this is fixed in eventlet 0.32.0: https://github.com/eventlet/eventlet/issues/619 Did you face the same bug? Any idea about how to fix that? Thanks a lot, Philippe Trace below: ERROR:lava_scheduler_app:[Errno -3] Lookup timed out Traceback (most recent call last): File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 435, in resolve return _proxy.query(name, rdtype, raise_on_no_answer=raises, File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 391, in query return end() File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 370, in end raise result[1] File "/usr/lib/python3/dist-packages/eventlet/support/greendns.py", line 351, in step a = fun(*args, **kwargs) File "/usr/lib/python3/dist-packages/dns/resolver.py", line 1089, in query return self.resolve(qname, rdtype, rdclass, tcp, source, File "/usr/lib/python3/dist-packages/dns/resolver.py", line 1043, in resolve timeout = self._compute_timeout(start, lifetime) File "/usr/lib/python3/dist-packages/dns/resolver.py", line 950, in _compute_timeout raise Timeout(timeout=duration) dns.exception.Timeout: The DNS operation timed out after 5.104917526245117 seconds

3 years, 7 months

2
1
0 0

Using Connection timeout for expected silence time on shell

by Paweł Wieczorek

Hi Lava Users, I'm working on a LAVA test that is not very chatty (little to no output during execution). I'm looking for a way to set expected silence time in that test and break its execution in case it's exceeded. I thought Connection timeout [1] would be my solution but by setting: timeouts: connections: lava-test-shell: seconds: 5 I was unable to get any difference in the job execution. I intentionally made timeout ridiculously small to see how it would affect the job. Please let me know if using Connection timeout for this purpose is a dead end. I'm also open for any solution suggestions (wrapping test with a script that would emit checkpoints on serial?) [1] https://lava.readthedocs.io/en/latest/technical-references/job-definition/t… Thanks, Paweł Wieczorek

3 years, 8 months

1
0
0 0

Alternate Bank booting support on NXP Layerscape boards

by Sahil Malhotra

Hi, We are working on integrating NXP Layerscape boards in LAVA. On Layerscape boards, we have a mechanism of having multiple banks. This is done mainly to protect board from getting bricked if wrong images gets flashed on board. Board is set to boot from a Bank 1 by default (controlled by switches). Now you use this bank also to flash your images, but in case the images are corrupt, board will get bricked and you will need to connect JTAG to recover the board. So here concept of Alternate Bank boot comes to help. By default board boots from Bank 1, but we will not flash the images on Bank 1, instead we will flash images on Bank 2. After flashing the images, we will boot from Bank 2 with a certain command on u-boot "qixis_reset altbank". With this command, Board boots from the Bank 2 and now we can boot up kernel on board. Since in this case, we have flashed the images on Bank 2 and even if images are corrupt, Bank 2 will get bricked, but since we have set board to boot from Bank 1 by default, Board will still be usable and you can flash the correct images on Bank 2 and get that working. So this was the concept and why we are using it. Now when we try to replicate the same behavior with LAVA, we are facing some issues. When we issue command "qixis_reset altbank" on u-boot, it just prints "=>", which lava takes as a success and issue next command and then starts waiting for the "Starting Kernel", which will not happen. Infact what should happen is that, after "qixis_reset altbank" is issued, lava should wait for some time and let board boot from Bank 2 (On Bank 2 board again will boot the u-boot only). and wait for "Hit Any key to stop autoboot" and then interrupt the board. Here is job.yaml for your reference. https://git.lavasoftware.org/lava/lava/uploads/2a530894990eca6c69648e6ad637… Please help me on this, how can i achieve this way of booting the board. Thanks Sahil Malhotra

3 years, 8 months

1
0
0 0

Error of results.get_testcase_results_yaml

by Larry Shen

Hi, guys, When I call `results.get_testcase_results_yaml`, there is a small probability that I will get the error: Post https://xiaotian:***@lava.sw.nxp.com/RPC2: EOF What does "EOF" here mean, what could be the possible root cause? Thanks.

3 years, 8 months

1
0
0 0

Any method to directly get device name from test shell?

by Larry Shen

Hi, guys, In lava, if we define e.g. "imx8mm-evk-sh01.jinja2" device dict, and run a job on this device, if possible we could get the name (imx8mm-evk-sh01) of this device directly in test shell? I don't want to define environment again and again in jinja2 file something like "{% set environment = {'DEVICE_NAME': " imx8mm-evk-sh01"} %}"..., there possible fault & mismatch when define this. Thanks.

3 years, 9 months

1
0
0 0

Android iperf test hung.

by Hedy Lamarr

Dear community, We are new to lava and try to use lava in our android test. We have issues when test iperf. Job: job_name: android iperf test timeouts: job: minutes: 10080 action: minutes: 120 connection: minutes: 5 priority: medium visibility: public protocols: lava-multinode: roles: device: count: 1 device_type: dragonboard-410c timeout: minutes: 5 host: count: 1 device_type: ssh timeout: minutes: 5 context: ssh_host: localhost ssh_user: root ssh_port: 22 ssh_identity_file: /root/.ssh/id_rsa actions: - deploy: role: - host timeout: minutes: 2 to: ssh os: debian - boot: role: - host method: ssh connection: ssh prompts: - '@labpc1' - test: role: - host timeout: minutes: 120 definitions: - from: inline name: smoke-case path: inline/test.yaml repository: metadata: format: Lava-Test Test Definition name: smoke description: Run smoke case run: steps: - sleep 60 - lava-send "server_ready" - iperf -s -V -P 1 - test: role: - device definitions: - from: inline name: cts_cts-media_test path: inline/cts_cts-media_test.yaml repository: metadata: description: cts cts-media test run format: Lava-Test Test Definition 1.0 name: cts-cts-media-test-run run: steps: - adb wait-for-device - adb devices - adb root - adb wait-for-device - adb devices - lava-wait "server_ready" - sleep 3 - lava-test-case "Case1" --shell adb shell /data/local/iperf -c 10.191.253.21 -t 10 docker: image: terceiro/android-platform-tools timeout: minutes: 4200 The job log for dragonboard-410c is: + lava-wait server_ready <LAVA_WAIT_DEBUG preparing Wed Jun 8 10:07:22 CST 2021> <LAVA_WAIT_DEBUG started Wed Jun 8 10:07:22 CST 2021> <LAVA_MULTI_NODE> <LAVA_WAIT server_ready> <LAVA_WAIT_DEBUG finished Wed Jun 8 10:07:22 CST 2021> <LAVA_WAIT_DEBUG finished Wed Jun 8 10:07:22 CST 2021> <LAVA_WAIT_DEBUG starting to wait Wed Jun 8 10:07:22 CST 2021> NOTE: it looks hung at this step, the job can't continue. The job log for ssh is: + lava-send server_ready <LAVA_SEND_DEBUG lava_multi_node_send preparing Wed Jun 8 10:07:53 CST 2021> <LAVA_SEND_DEBUG _lava_multi_node_send started Wed Jun 8 10:07:53 CST 2021> <LAVA_MULTI_NODE> <LAVA_SEND server_ready> Received Multi_Node API <LAVA_SEND> messageID: SEND-server_ready lava-multinode lava-send Handling signal <LAVA_SEND {"request": "lava_send", "messageID": "server_ready", "message": {}, "timeout": 300}> Setting poll timeout of 300 seconds requesting lava_send server_ready message: {} requesting lava_send server_ready with args {} request_send server_ready {} Sending {'request': 'lava_send', 'messageID': 'server_ready', 'message': {}} final message: {"port": 3079, "blocksize": 4096, "poll_delay": 3, "host": "10.191.253.109", "hostname": "lavaslave1", "client_name": "3035", "group_name": "8a362e2a-6ee9-4f48-bddb-378ac2425f06", "role": "host", "request": "lava_send", "messageID": "server_ready", "message": {}} Connecting to LAVA Coordinator on 10.191.253.109:3079 timeout=300 seconds. case: multinode-send-server_ready case_id: 39177 definition: 0_smoke-case result: pass <LAVA_SEND_DEBUG _lava_multi_node_send finished Wed Jun 8 10:07:53 CST 2021> <LAVA_SEND_DEBUG lava_multi_node_send finished Wed Jun 8 10:07:53 CST 2021> + iperf -s -V -P 1 ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 85.3 KByte (default) ------------------------------------------------------------ It seems that one node can't receive server-ready from another node, what's wrong with my job? Please help! Thanks, Hedy Lamarr

3 years, 9 months

2
13
0 0

How to exit job in advance.

by Larry Shen

Hi, guys, We have a scenario like next: action: - test definitions: - from: inline name: test1 - test definitions: - from: inline name: test2 For some reasons, we have to use 2 tests here, everything is ok now. But, if `test1`, that is ` /lava-3102/0/tests/0_test1/run.sh` finished with non-zero, from web we can see the suite fail. Then, we want to exit the job at once, not continue to run `test2`. If possible here? Regards, Larry

3 years, 10 months

2
2
0 0

Set boot settings with x86 / PXE

by Fabiano Ferronato

Hi everybody, I'm trying to figure out how to set boot parameters (nfsroot) for a x86 board (Intel NUC10 ). >From this job definition I understand it's possible using iPXE: https://lkft.validation.linaro.org/scheduler/job/2959364/definition But I can't understand what interface is being used to get terminal output and remote control: https://lkft.validation.linaro.org/scheduler/device/x86-01/devicedict Look's like is using UART, I'm not sure I can get terminal console on boot time on my board (NUC). The options I can get from the information found are the following (please add any corrections or suggestions): 1) iPXE + terminal console: PXE alone can't get nfsroot settings dynamically. PXE + iPXE should be added to the chain and LAVA should have access to terminal console. 2) iPXE + environment variables: LAVA sets environment variables and PXE + iPXE gets nfsroot settings from environment variables. No terminal console needed. 3) PXE + static folder: LAVA fetches and extract rootfs always to the same folder. PXE reads static configuration file. 4) PXE + dynamic folder: LAVA sets the nfsroot folder name directly on the PXE configuration file (file is machine specific). 5) PXE + INITRAMFS: fetches root file system from file server and extracts to memory. Let me know your thoughts! Best Regards Fabiano

3 years, 10 months

2
1
0 0

Difference of next 2 docker options.

by Hedy Lamarr

Dear, I'm a little confused about the next 2 options: a) https://lava.readthedocs.io/en/latest/user/advanced-tutorials/running-arbit… b) https://lava.readthedocs.io/en/latest/admin/basic-tutorials/device-setup/do… It seems they both run a docker container on pc, what's the difference between them? Could one replace another? What I expect to get is something like: for xx scenario, you need to use option a, while for xxx scenario, you need to use option b. Thanks, Hedy Lamarr

3 years, 10 months

2
1
0 0

Providing Arguments from Job to Test Shell (definition?)

by Westermann, Oliver

Hey, We're using lava to test multiple of our devices. While most tests are similar ("does the device still have a working ethernet connection"), some slightly differ. For example a device might have LEDs 1-3, another the LEDs 1-5. Today I save multiple test shell definitions test1-device1.yaml, test1-device2.yaml, ..., which all just differ by providing "device1", "device2", ... in an argument to the actual test script, so the run: section looks like this: run: steps: - cd ./testdir/ - ./run_test.py device1 I would like to get rid of the two, separate .yaml files and only have a `./run_test.py ${device}` or similar. Is there any way to provide a variable from the job definition to the test shell definition? Or are things like the device type set in the environment so I could access them? Best regards, Olli

3 years, 10 months

2
4
0 0

How to quickly find other guys' job.

by Hedy Lamarr

Dear, I wonder if it is possible on the job page, I could quickly find other guys' jobs with a search function? I tried next, but returned nothing. owner_query=hedy.lamarr Thanks, Hedy Lamarr

3 years, 10 months

3
4
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users