lava-users

lava-users@lists.lavasoftware.org

1 participants
912 discussions

Re: [Lava-users] None of the deployment strategies accepted your deployment parameters

by dhanu msys

Hi Milosz, Thanks for the reply. I will try to get the eth008 if possible , otherwise i will try to make use of TFTP or u-boot methods to run the test job on STM32mp157c-dk2. Thanks & Regards, Dhanunjaya. P On Mon, Nov 11, 2019 at 4:57 PM Milosz Wasilewski < milosz.wasilewski(a)linaro.org> wrote: > On Mon, 11 Nov 2019 at 11:07, dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > > > > Hi Milosz, > > > > Really Thanks for sharing the Information. > > > > I have basic question, we can't able to run any test job for the STM32 > without external hardware(PDU) ? > > > > Can you please share the device configuration , which helps to run the > test jobs without "ethernet controlled relay" for the STM32. > > > https://git.linaro.org/lava/lava-lab.git/tree/shared/lab-scripts/eth008_con… > > > > > As I requested earlier , is there any possibility to run the STM32 > specific jobs with any other deployment methods(tmpfs , tftp..etc). > > Our boards use EFI for booting and I never tried tftp with that. You > might need grub EFI application for that. Alternatively you might use > u-boot. I didn't try that either. > > milosz > > > > > Thanks & Regards, > > Dhanunjaya. P > > > > > > On Mon, Nov 11, 2019 at 4:19 PM Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> wrote: > >> > >> Well, LAVA will try to switch the device into DFU mode for deployment > >> step. These lines in the device dict do it: > >> '/usr/local/lab-scripts/eth008_control -a 172.27.19.27 -r 1 -s on', > >> '/usr/local/lab-scripts/eth008_control -a 172.27.19.27 -r 2 -s on', > >> Then it will power on the board: > >> '/usr/local/lab-scripts/snmp_pdu_control --hostname lngpdu01 --command > >> on --port 3 --delay 20', > >> After that it will try to flash it using the STM32_Programmer_CLI: > >> '/usr/local/bin/STM32_Programmer_CLI -c port=usb1 -w {LAYOUT} -q', > >> Lastly it will power the board down and flip the dip switches back: > >> '/usr/local/lab-scripts/snmp_pdu_control --hostname lngpdu01 --command > >> off --port 3', > >> '/usr/local/lab-scripts/eth008_control -a 172.27.19.27 -r 1 -s off', > >> '/usr/local/lab-scripts/eth008_control -a 172.27.19.27 -r 2 -s off', > >> > >> So if you don't have HW moded board, this device dict won't work for > >> you. Sources for the scripts are here: > >> https://git.linaro.org/lava/lava-lab.git/tree/shared/lab-scripts > >> We're using pretty expensive HW in the LAB: > >> - managed APC PDUs: > >> > https://www.apc.com/shop/uk/en/products/Rack-PDU-Switched-1U-16A-208-230V-8… > >> (I couldn't find the exact models we have, they're discontinued) > >> - ETH008 relay board: > https://www.robot-electronics.co.uk/htm/eth008tech.htm > >> > >> milosz > >> > >> On Mon, 11 Nov 2019 at 10:42, dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > >> > > >> > Hi Milosz, > >> > > >> > No. > >> > Through Manual Setup , we are able to switch between the modes. > >> > > >> > Here I have attached the kernel & dtb image for your reference. PFA. > >> > > >> > Dhanunjaya. P > >> > > >> > > >> > On Mon, Nov 11, 2019 at 3:40 PM Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> wrote: > >> >> > >> >> I think I forgot to ask key question when it comes to this device: > did > >> >> you do the HW mod to be able to switch between DFU and OS boot modes > >> >> without manual step? > >> >> > >> >> milosz > >> >> > >> >> On Mon, 11 Nov 2019 at 10:01, dhanu msys <dhanuskd.palnati(a)gmail.com> > wrote: > >> >> > > >> >> > Hi Milosz, > >> >> > > >> >> > Thanks for reply. > >> >> > > >> >> > I am new to the LAVA usage. > >> >> > > >> >> > I have taken reference from the below link. > >> >> > > https://staging.validation.linaro.org/scheduler/device/staging-stm32mp157-0… > >> >> > > >> >> > Here I have attached the device_dictionary & device configurations > files, PFA. > >> >> > > >> >> > Note : I am not able to see the "lab-scripts" to have power > controlled commands in my local repository , is there any specific package > need to install in my localhost , can you please share the lab-scripts to > have pdu control and also please share the pdu device details if required > to connect with the hardware. > >> >> > > >> >> > Can you please share some references , which i can run some jobs > through any other deploy methods like "tmpfs , tftp " for "STM32MP157C-DK2". > >> >> > > >> >> > Thanks & Regards, > >> >> > Dhanunjaya. P > >> >> > > >> >> > > >> >> > On Mon, Nov 11, 2019 at 2:59 PM Milosz Wasilewski < > milosz.wasilewski(a)linaro.org> wrote: > >> >> >> > >> >> >> Could you share your device dictionary? You might be missing > >> >> >> flasher_deploy_commands. > >> >> >> > >> >> >> Please check here for reference: > >> >> >> > https://ledge.validation.linaro.org/scheduler/device/lng-stm32mp157-01/devi… > >> >> >> > >> >> >> milosz > >> >> >> > >> >> >> On Thu, 7 Nov 2019 at 07:48, dhanu msys < > dhanuskd.palnati(a)gmail.com> wrote: > >> >> >> > > >> >> >> > Hi Team, > >> >> >> > > >> >> >> > I am trying to run the test_jobs on the specific device type > "stm32mp1157c-dk2" , but its throwing an error message to deploy "flasher" > method in the deployment parameters. > >> >> >> > > >> >> >> > Here I have attached the screenshots for reference. PFA. > >> >> >> > > >> >> >> > Thanks & Regards, > >> >> >> > Dhanunjaya. P > >> >> >> > _______________________________________________ > >> >> >> > Lava-users mailing list > >> >> >> > Lava-users(a)lists.lavasoftware.org > >> >> >> > https://lists.lavasoftware.org/mailman/listinfo/lava-users >

5 years, 1 month

Fork option is disabled

by Suram Suram

Hi, I want to submit a change to device-type file and when I tried from the webGUI after logging in, the fork option is disabled. After clicking on the forks count number, the fork option appears to be enabled on that page. Clicked it to select namespace, when hovered the mouse over the namespace, it shows the following error "You have reached your project limit" Can some one help me on this please? Regards Suram

5 years, 1 month

None of the deployment strategies accepted your deployment parameters

by dhanu msys

Hi Team, I am trying to run the test_jobs on the specific device type "stm32mp1157c-dk2" , but its throwing an error message to deploy "flasher" method in the deployment parameters. Here I have attached the screenshots for reference. PFA. Thanks & Regards, Dhanunjaya. P

5 years, 1 month

Force prompt in lava boot issue.

by Larry Shen

Guys, We have a problem as next: [cid:image001.jpg@01D5958F.E65E7670] The story is we have kernel exception when device boot, then per next code: if index == cls.TRACE or index == cls.EXCEPTION: res = "fail" if action: action.logger.warning( "%s: %s" % (action.name, cls.MESSAGE_CHOICES[index][2]) ) # TRACE may need a newline to force a prompt connection.sendline(connection.check_char) It will send a "#" to device, but unfortunately, the exception time is too close the final login, then the "#" was sent to user login as next: Imx8qxpmek login: # Then when we send "root", it definitely cannot login, how to resolve? More, why lava send "#" to device when kernel have exception?

5 years, 1 month

Re: [Lava-users] 500 internal server error

by Remi Duraffort

Hello, could you give me the exact version? If you are admin, just ask debian to give you the package version. If you are a user, this is printed in the first line of every job logs. Rgds Le lun. 4 nov. 2019 à 07:58, dhanu msys <dhanuskd.palnati(a)gmail.com> a écrit : > Hi Remi, > > I was using LAVA Version V2, please correct me if i am quite wrong. > > Please let me know how to find out the lava version using command prompt. > > Thanks & Regards, > Dhanunjaya. P > > > On Thu, Oct 31, 2019 at 9:42 PM Remi Duraffort <remi.duraffort(a)linaro.org> > wrote: > >> Hello, >> >> which version are you using? >> >> >> Rgds >> >> Le jeu. 31 oct. 2019 à 13:19, dhanu msys <dhanuskd.palnati(a)gmail.com> a >> écrit : >> >>> Hi Team, >>> >>> While Running LAVA in localhost , facing the error while accessing the >>> UI related to Devices. >>> >>> Here I have attached the screenshot , please find the attachment. >>> >>> Please help me to solve this issue. >>> >>> Thanks & Regards, >>> Dhanunjaya. P >>> _______________________________________________ >>> Lava-users mailing list >>> Lava-users(a)lists.lavasoftware.org >>> https://lists.lavasoftware.org/mailman/listinfo/lava-users >> >> >> >> -- >> Rémi Duraffort >> LAVA Architect >> Linaro >> > -- Rémi Duraffort LAVA Architect Linaro

5 years, 1 month

Lava Test Jobs didn't scheduled

by dhanu msys

Hi Team, I have submitted some sample test jobs for qemu device type on my local lava setup. After successful submission of tests , I can't able to see the jobs running status , the state remains to "submitted". When i gone through the lava-master logs , Observed the warnings saying that can't able to schedule the jobs due to lava-logs is offline. Here I have attached the screenshots. Please find the attachments. Can you please let me know how to schedule the jobs on master by manual. Thanks & Regards, Dhanunjaya. P

5 years, 1 month

Issue with prompt matching with no output during boot

by Diego Russo

Hello, We upgrade from LAVA 2019.04 to 2019.10 and we have issues with the prompt matching when the device boots. We test 2 kinds of Linux images: * Development image * it outputs data into the serial (secure boot, uboot, kernel, systemd) * user: root, pass: empty * Production image * it doesn't output anything and *only presents the login prompt* * user: root, pass: it could be anything The workflow is the following: * spin up LXC container for recovery mode * boot the DUT waiting for the prompt. We don't need to login using the serial connection but we need to wait the prompt to understand that the board has successfully booted * run tests from the LXC container and using ssh to the DUT In LAVA 2019.04 everything was working as expected: ... start: 7.3 auto-login-action (timeout 00:05:57) [target] Using line separator: #'\n'# No login prompt set. Parsing kernel messages ['-+\\[ cut here \\]-+\\s+(.*\\s+-+\\[ end trace (\\w*) \\]-+)', '(Unhandled fault.*)\\r\\n', 'Kernel panic - (.*) end Kernel panic', 'Stack:\\s+(.*\\s+-+\\[ end trace (\\w*) \\]-+)', 'mbed-linux-os-(.*) login:', 'Login timed out', 'Login incorrect'] [auto-login-action] Waiting for messages, (timeout 00:05:57) Waiting using forced prompt support. 178.45381999015808s timeout Trying ::1... Connected to localhost. Escape character is '^]'. Mbed Linux OS mbl-warrior-dev-production_build64 mbed-linux-os-674 ttymxc5 Matched prompt #4: mbed-linux-os-(.*) login: ... While in 2019.10 the job is failing with the following: ... start: 7.3 auto-login-action (timeout 00:05:57) [target] auto-login-action: Wait for prompt ['Linux version [0-9]'] (timeout 00:06:00) Trying ::1... Connected to localhost. Escape character is '^]'. � Mbed Linux OS mbl-warrior-dev-production_build74 mbed-linux-os-1764 ttymxc5 ... Another thing we observed in LAVA 2019.10: using the dev images (hence with output data) it works without any problem. Here a snippet of our pipeline: .... - boot: namespace: recovery timeout: minutes: 5 method: recovery commands: recovery - deploy: timeout: minutes: 10 to: recovery namespace: recovery connection: lxc images: images to download..... os: debian - test: namespace: lxc connection: lxc timeout: minutes: 10 definitions: - from: inline name: flash-image path: inline/flash-image.yaml repository: metadata: format: Lava-Test Test Definition 1.0 name: flash-image description: "Flash image to board in recovery mode" os: - oe run: steps: - steps to recover the board - boot: namespace: recovery timeout: minutes: 5 method: recovery commands: exit - boot: namespace: target method: minimal failure_retry: 3 prompts: - "mbed-linux-os-(.*) login:" timeout: minutes: 6 .... Looking at the LAVA code we think the following commit changed the behaviour: https://git.lavasoftware.org/lava/lava/commit/6b5698a2d3ed23031e40aa1d86181… How are we supposed to change the pipeline to make it work again? Thanks -- Diego Russo | Staff Software Engineer | Mbed Linux OS ARM Ltd. CPC1, Capital Park, Cambridge Road, Fulbourn, CB21 5XE, United Kingdom http://www.diegor.co.uk - https://os.mbed.com/docs/mbed-linux-os/ 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.

5 years, 1 month

Unexpected crash.

by cnspring2002

Hi, Sometimes, lava master will show next error, then seems zemomq crash, do you know what's the potential cause? 2019-08-20 09:14:39,576 DEBUG lava-worker-1 => PING(20) 2019-08-20 09:14:39,578 DEBUG lava-worker-2 => PING(20) 2019-08-20 09:14:39,580 DEBUG lava-worker-3 => PING(20) 2019-08-20 09:14:44,467 ERROR [CLOSE] Unknown exception raised, leaving! 2019-08-20 09:14:44,467 ERROR 'utf-8' codec can't decode byte 0xc0 in position 10: invalid start byte Traceback (most recent call last): File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 687, in handle self.main_loop(options) File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 731, in main_loop while self.controler_socket(): # Unqueue all pending messages File "/usr/lib/python3/dist-packages/lava_server/management/commands/lava-master.py", line 234, in controler_socket hostname = u(msg[0]) File "/usr/lib/python3/dist-packages/zmq/utils/strtypes.py", line 34, in cast_unicode return s.decode(encoding, errors) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc0 in position 10: invalid start byte 2019-08-20 09:14:44,467 INFO [CLOSE] Closing the controler socket and dropping messages

5 years, 1 month

About associated log lines in suite page.

by Larry Shen

All, I'm testing some feature about associated log lines in lava, job.yaml is as follows. Job.yaml: - test: connection: lxc definitions: - from: inline name: my_suite path: me.yml repository: metadata: format: Lava-Test Test Definition 1.0 name: smoke-case-run description: Run smoke case run: steps: - lava-test-case "Case001" --shell 'echo wow' - lava-test-case "Case002" --shell 'ls' namespace: lxcEnv timeout: minutes: 10 1. Then, let's see next picture of Case001: [cid:image002.jpg@01D59322.5F8C2990] it said startline=153, lastline=154, that's next: Line153 is "Received signal: <STARTTC> Case001", Line 154 is "Received signal: <ENDTC> Case001". You could see in fact the log "wow" not in the 2 lines. [cid:image008.jpg@01D59322.5F8C2990] 2. let's see next picture of Case002: [cid:image009.jpg@01D59322.5F8C2990] It said startline=160, lastline=163, that's next: [cid:image010.jpg@01D59322.5F8C2990] It's ok, that between Ln160 & Ln163 I got the output of `ls`. What happened for "Case001"? The startline & endline not correct. It seems if I directly do "echo", the info is wrong. while "execute command", the info is correct. Of course my case will not just do "echo", just I want to know if any risk for me to fetch the wrong START/LAST lines in other scenario? (I will use script to fetch it with xmlrpc).

5 years, 1 month

removing support for boot['type']

by Milosz Wasilewski

Hi, When test job uses boot action with method: u-boot there was an option to tell it which boot command to call in u-boot shell. This was done using 'type' parameter. Example from docs: - boot: method: u-boot commands: nfs type: bootz prompts: - 'root@debian:~#' This parameter was deprecated for more than a year. I just submitted a patch to remove this feature. If you're using it, please consider changing to setup where kernel image type is set using deploy section. Example: - deploy: timeout: minutes: 4 to: tftp os: oe kernel: url: 'https://example.com/zImage' type: 'zimage' dtb: url: 'https://example.com/dtb.dtb' nfsrootfs: url: 'https://example.com/rootfs.tar.xz' compression: xz Pull request: https://git.lavasoftware.org/mwasilew/lava/pipelines/5794 milosz

5 years, 1 month

← Newer
1
...
31
32
33
34
35
36
37
...
92
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

lava-users