Lava-users May 2018

lava-users@lists.linaro.org

17 participants
19 discussions

by Hemanth K V

Hello Lava-Users, I have UEFI based x86 target board which I want to connect to LAVA and execute tests. When I go through https://validation.linaro.org/static/docs/v2/integrate-uefi.html it specifies different mechanism available.I am confused here as I am not completely clear on differences between systems mentioned. If I just know UEFI implementations method of target is it enough to select which method can be used for booting. What are the things I need to know before concluding the method to be used for booting x86 based target board? Thanks, Hemanth.

6 years

Re: [Lava-users] Running large test suites

by Tim Jaacks

Hi Dan, >Here's an example of generating lava templates using jinja2. It's probably more complicated than you need. > >See >https://git.linaro.org/ci/job/configs.git/tree/openembedded-lkft/lava-job-d… >for a directory of templates, and see >https://git.linaro.org/ci/job/configs.git/tree/openembedded-lkft/submit_for… >for the python code that does the generation. Lastly, you can run https://git.linaro.org/ci/job/configs.git/tree/openembedded-lkft/test_submi… >and it will generate all of the YAML files into "./tmp". > >Like I said, this is likely more complicated than you are looking for. I suggest starting simpler using https://pypi.python.org/pypi/jinja2-cli/0.6.0. Thank you, that really helps a lot. We want to trigger the LAVA jobs from Jenkins as well, and we need lots of metadata because the tests will be part of our release notes in the end. So no, this is definitely not more complicated than we need. In fact, this is a very good starting point for us. You should think about adding a chapter to the LAVA documentation about how to generate YAML job submissions via templates. I assume we are not the only ones facing this problem. And I had basically no experience with jinja2 at all before evaluating LAVA, so I would not have come up with the idea of using this mechanism for the job submissions myself. 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 SOLUTIONS THAT COMPLETE! Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz

6 years

question about result parse pattern in monitor action

by Chase Qi

Hi, To match the result lines in the following log from zephyr sanity test: — output — ***** Booting Zephyr OS v1.11.0-1194-g4b0b65c1b ***** Running test suite poll_api =================================================================== starting test - test_poll_no_wait PASS - test_poll_no_wait =================================================================== starting test - test_poll_wait PASS - test_poll_wait =================================================================== starting test - test_poll_multi PASS - test_poll_multi =================================================================== =================================================================== — output ends — I started with this pattern: '(?P<result>(PASS|FAIL))\s-\s(?P<test_case_id>\w+)', but the test_case_ids it matched are incomplete, shown as below. Refer to https://validation.linaro.org/scheduler/job/1807112 test_po test_poll_ test_poll_mu I also tried the following patterns, but no lucky. '(?P<result>(PASS|FAIL))\s-\s(?P<test_case_id>\w+)$’ matched sth similar as above, but the not the same. Refer to https://validation.linaro.org/scheduler/job/1807117 '(?P<result>(PASS|FAIL))\s-\s(?P<test_case_id>\w+)\n’ didn’t match anything. A search online hit https://stackoverflow.com/questions/14689531/how-to-match-a-new-line-charac… . Then I tried manually in python shell. '(?P<result>(PASS|FAIL))\s-\s(?P<test_case_id>\w+)’ works, '(?P<result>(PASS|FAIL))\s-\s(?P<test_case_id>\w+)$’ works only when re.M enabled. — debug — >>> s "\nTrying ::1...\nConnected to localhost.\nEscape character is '^]'.\nFRDM-KW41Z-01 7113 [115200 N81]\n***** Booting Zephyr OS v1.11.0-1194-g4b0b65c1b *****\nRunning test suite poll_api\n===================================================================\nstarting test - test_poll_no_wait\nPASS - test_poll_no_wait\n===================================================================\nstarting test - test_poll_wait\nPASS - test_poll_wait\n===================================================================\nstarting test - test_poll_multi\nPASS - test_poll_multi\n===================================================================\n===================================================================\n" >>> p.search(s).group() 'PASS - test_poll_no_wait' >>> p = re.compile(r'(?P<result>(PASS|FAIL))\s-\s(?P<test_case_id>\w+)$') >>> p.search(s).group() Traceback (most recent call last): File "<stdin>", line 1, in <module> AttributeError: 'NoneType' object has no attribute 'group' >>> p = re.compile(r'(?P<result>(PASS|FAIL))\s-\s(?P<test_case_id>\w+)$', re.M) >>> p.search(s).group() 'PASS - test_poll_no_wait’ — ends — Could you please advise me how to handle the parsing with the monitor action? Thanks, Chase

6 years, 1 month

u-boot devices broken after 2018.4 upgrade, strange u-boot interaction

by Kevin Hilman

Hello, After upgrading to 2018.4 (also tried .5) many of our device-types using base-uboot.jinja2 are broken. While I really like the major improvement to run commands individually, there seems to be some problems and the LAVA output logs are very confusing, showing concatenated strings, etc. Here is an example for an upstream device-type (meson-gxbb-p200), and here is where it starts interacting with u-boot: http://khilman.ddns.net/scheduler/job/15#L336 The "Parsed boot commands" look perfect, and all the commands in black all look good, but notice the commands at the u-boot prompt, they appear to be concatenated, starting right away at the "setenv initrd_high ..." However, observing the commands on the actual serial port (I use conmux, so can observe the serial console interactions directly), I'm not seeing concatenated strings, but the "setenv serverip ..." never shows up, so the TFTP downloads fail, and the job fails. Here's what I see directly on the serial console: Hit Enter or space or Ctrl+C key to stop autoboot -- : 0 gxb_p200_v1# gxb_p200_v1#setenv autoload no gxb_p200_v1#setenv initrd_high 0xffffffff gxb_p200_v1#setenv fdt_high 0xffffffff gxb_p200_v1#dhcp dwmac.c9410000 Waiting for PHY auto negotiation to complete.. done Speed: 100, full duplex BOOTP broadcast 1 BOOTP broadcast 2 DHCP client bound to address 192.168.0.216 (267 ms) gxb_p200_v1#tftp 0x1080000 14/tftp-deploy-5v1wo7fv/kernel/uImage Speed: 100, full duplex Using dwmac.c9410000 device TFTP from server 192.168.0.1; our IP address is 192.168.0.216 Filename '14/tftp-deploy-5v1wo7fv/kernel/uImage'. Load address: 0x1080000 Loading: * TFTP error: 'File not found' (1) Even more interesting is that on the same setup, a beaglebone-black device, using the same base-uboot.jinja2 is working just fine: http://khilman.ddns.net/scheduler/job/1 Any help would be appreciated, I'm thoroughly confused by what's going on here. Thanks, Kevin

6 years, 1 month

QEMU health check apparently not running

by Robert Marshall

At some point last week - I think because of network connectivity issues a job got stuck and I I cancelled it, it when run again it again appeared to hang. I again cancelled it and am now seeing the health check not start (at least no output appears on the job's webspage. Looking at the output.yaml (in /var/lib/lava-server/default/media/job-output/2018/05/23/32 ) I see ... progress output for downloading https://images.validation.linaro.org/kvm/standard/stretch-2.img.gz - {"dt": "2018-05-23T07:39:54.728015", "lvl": "debug", "msg": "[common] Preparing overlay tarball in /var/lib/lava/dispatcher/tmp/32/lava-overlay-aye3n2ke"} - {"dt": - "2018-05-23T07:39:54.728root@stretch:/var/lib/lava-server/default/media/job-output/2018/05/23/32 But none of this appears in http://localhost:8080/scheduler/job/32 and at the head of that page I see the message: Unable to parse invalid logs: This is maybe a bug in LAVA that should be reported. which other logs are best for checking whether this is an error that should be fed back? (LAVA 2018.4) Robert

6 years, 1 month

Unable to run test on multiple devices using Lava-multi-node functionality

by Onkar Bokshe

Hi All, I am trying to run test on multiple ssh devices using multi-node functionality(protocols,tags and ssh connection) , device is detected in multi-node information as below but no unable to get the debug log i.e no actions are processing after devices detection please help me to resolve this. Following is working fine a) I am able to run test using single node on both devices b) Framework detects devices mentioned in protocols as mentioned below Mulitnode info : 125.0 <http://134.86.62.95/scheduler/job/125.0> (125) on: uno-ssh <http://134.86.62.95/scheduler/device/uno-ssh> as: node1 125.1 <http://134.86.62.95/scheduler/job/125.1> (126) on: nano-mel <http://134.86.62.95/scheduler/device/nano-mel> as: node2 125.2 <http://134.86.62.95/scheduler/job/125.2> (127) No device assigned as node2. Job Info is displaying : 13*6** Submitted* *ssh* python-test-suite obokshe May28, 8:47a.m. — — 12*5** Scheduling* uno-ssh <http://134.86.62.95/scheduler/device/uno-ssh> python-test-suite obokshe May28, 8:47a.m. — — *124 Scheduling* nano-mel <http://134.86.62.95/scheduler/device/nano-mel> python-test-suite obokshe May28, 8:47a.m. — — Please find test definition used by me for lava-multinode test run at https://pastebin.com/Tdp7q6SF Thanks and Regards, Onkar

6 years, 1 month

Unable to run test on multiple devices using Lava-multi-node functionality

by Onkar Bokshe

6 years, 1 month

Test on Device which doesn't stop at bootloader

by Nikita Gupta

Hi Lava-Users, I have a device 'raspberry-pi' whose boot method doesn't stop at bootloader. I tried removing 'method' from boot-action but then it doesn't accept it as valid test job. Changing of method from u-boot to fastboot or to any other also gives error as not supported boot methods for this device. After device bring up, it gives u-boot interrupt timed-out and job gets incomplete. Is there any way thru which we can run tests on such devices? -- Regards, Nikita Gupta

6 years, 2 months

multiple devices job submission

by Hemanth K V

Hello Stevan, Thanks for quick response.Is there any reference of creating and assigning device tag to specific device. The issue I am facing is whatever device tags are created are getting default assigned to all devices. Thanks, Hemanth. ___________________________________________________________________________________________ Hi Hemanth, You can achieve this by adding device tags to the devices and then specifying which tags you'd like to use in the test job definition. Please take a look at https://validation.linaro.org/static/docs/v2/developing-tests.html#device-t… HTH, On 05/16/2018 12:26 PM, Hemanth K V wrote: >* Hello Lava-Users, *>>* When we have multiple devices of same device-type in LAVA Instance and *>* want to submit job on a particular device how can this be achieved in *>* LAVA.Tried to follow *>* https://validation.linaro.org/static/docs/v2/first-job.html <https://validation.linaro.org/static/docs/v2/first-job.html> but didn't *>* find how device can be specified. *>>* Thanks, *>* Hemanth. *>>>* _______________________________________________ *>* Lava-users mailing list *>* Lava-users at lists.linaro.org <https://lists.linaro.org/mailman/listinfo/lava-users> *>* https://lists.linaro.org/mailman/listinfo/lava-users <https://lists.linaro.org/mailman/listinfo/lava-users> *

6 years, 2 months

multiple devices job submission

by Hemanth K V

Hello Lava-Users, When we have multiple devices of same device-type in LAVA Instance and want to submit job on a particular device how can this be achieved in LAVA.Tried to follow https://validation.linaro.org/static/docs/v2/first-job.html but didn't find how device can be specified. Thanks, Hemanth.

6 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Lava-users May 2018