lava-users June 2021

lava-users@lists.lavasoftware.org

10 participants
14 discussions

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

2 years, 3 months

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

2 years, 11 months

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

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

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

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

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

Device status not correct.

by Hedy Lamarr

Dear all, I don't know what operation I have done, but when a device does not have any running job, I still see the device is in running status. I just saw this 1 time, maybe it's a bug or just bad luck. Anyway, I can't reproduce it on other devices, so it's ok. But, could you teach me to reset the status to make the device work again? Do we have some method to reset the status from "Running" to "Idle", or any api if we don't have an interface on the UI? [image: image.png] Thanks, Hedy Lamarr

3 years, 1 month

Unable to get kernel boot messages in to lava job while using lava framework & telnet

by Nagendra Singamsetti

Hi , I am trying to automate the linux boot functionality on my custom boards using LAVA framework. Previously I have done it on Renesas board using LAVA it works fine.I got linux boot messages on lava job whereas i am not getting with customised board. *Issue: *I am using trace32 debugger to flash images onto the board (working fine). After that i am calling minimal method in pipeline job to get prompt strings/login But i am not getting the linux boot messages on the job. always stucks at the following: [common] connect-device Connecting to device using 'telnet 10.10.0.18 4000' <http://10.10.0.69/scheduler/job/789#L136>Setting prompt string to ['lava-test: # '] <http://10.10.0.69/scheduler/job/789#L137>end: 2.3 connect-device (duration 00:00:00) [common] <http://10.10.0.69/scheduler/job/789#L138>end: 2 boot-trace32-image (duration 00:00:28) [common] <http://10.10.0.69/scheduler/job/789#action_3>start: 3 minimal-boot (timeout 00:03:00) [common] <http://10.10.0.69/scheduler/job/789#action_3-1>start: 3.1 connect-device (timeout 00:03:00) [common] <http://10.10.0.69/scheduler/job/789#L141>Already connected <http://10.10.0.69/scheduler/job/789#L142>end: 3.1 connect-device (duration 00:00:00) [common] <http://10.10.0.69/scheduler/job/789#action_3-2>start: 3.2 auto-login-action (timeout 00:03:00) [common] <http://10.10.0.69/scheduler/job/789#L144>Setting prompt string to ['Booting Linux'] <http://10.10.0.69/scheduler/job/789#L145>auto-login-action: Wait for prompt ['Booting Linux'] (timeout 00:03:00) <http://10.10.0.69/scheduler/job/789#L146>Trying 10.10.0.18... <http://10.10.0.69/scheduler/job/789#L147>Connected to 10.10.0.18. <http://10.10.0.69/scheduler/job/789#L148>Escape character is '^]'. <http://10.10.0.69/scheduler/job/789#L149> <http://10.10.0.69/scheduler/job/789#L150>alif_asic01 4000 [115200 N81] <http://10.10.0.69/scheduler/job/789#L151> <http://10.10.0.69/scheduler/job/789#L152>auto-login-action timed out after 180 seconds <http://10.10.0.69/scheduler/job/789#L153>end: 3.2 auto-login-action (duration 00:03:00) [common] *Both telnet & serial server(ser2net) is configured.* *Uart cable attached with serial server: usb-Profolic_Technology_Inc._Usb-serial_Controller-ifoo-port0* i am getting boot log messages using telnet manually but not with lava. *Manual log with telnet:* $ telnet 10.10.0.18 4000 Trying 10.10.0.18... Connected to 10.10.0.18. Escape character is '^]'. alif_asic01 4000 [115200 N81] Booting Linux on physical CPU 0x0 Linux version 5.4.25-00024-g9283a6810958-dirty (nishit@alif) (gcc version 9.2.0 (GCC)) #72 Tue Apr 20 15:41:31 IST 2021 #HGG1 CPU: ARMv8-a aarch32 Processor [411fd010] revision 0 (ARMv8), cr=50c5383d CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache #HGG1.1 OF: fdt: Machine model: corstone700 [PFA] yaml job thanks Regards Nagendra S

3 years, 1 month

About serial question.

by Hedy Lamarr

Dear, Recently I'm learning and evaluating LAVA to see if it can help us. I saw next from https://validation.linaro.org/static/docs/v2/connections.html: {% set connection_list = ['uart0', 'uart1'] %}{% set connection_commands = {'uart0': 'telnet dispatcher01 7001', 'uart1': 'telnet dispatcher01 7002'} %} I'm pretty confused by the 'uart0', 'uart1'. Should I explicitly specify something in my job to let some action to choose 'uart0' or 'uart1'? How does LAVA know at which time it should choose which uart? Thanks, Hedy Lamarr

3 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users June 2021