Hi Pawan,
It looks like we had a misunderstanding. I thought you wanted all your jobs to fail the same way. To revert this solution, just remove the "invalid partition" from device type. It looks like you're using some board with imx8mm chip. This is what lava sources show:
etc/dispatcher-config/device-types$ grep "Invalid partition" * am6.jinja2:{% set uboot_extra_error_message = 'Invalid partition' %} imx8m-common.jinja2:{% set uboot_extra_error_message = uboot_extra_error_message|default('Invalid partition') %} imx8q-common.jinja2:{% set uboot_extra_error_message = uboot_extra_error_message|default('Invalid partition') %} imx8u-common.jinja2:{% set uboot_extra_error_message = uboot_extra_error_message|default('Invalid partition') %} imx9-common.jinja2:{% set uboot_extra_error_message = uboot_extra_error_message|default('Invalid partition') %} sharkl2.jinja2:{% set uboot_extra_error_message = 'Invalid partition' %} x15.jinja2:{% set uboot_extra_error_message = 'Invalid partition' %}
I guess you can overwrite uboot_extra_error_message in the device dictionary. Alternatively add a new device type which overrides the uboot_extra_error_message and derive your devices from this new type.
Best Regards, Milosz
On Thu, Jan 11, 2024 at 5:57 AM pawanKumar pawan4749@gmail.com wrote:
Hi Milosz,
I tried this solution by adding in the job definition as a context and adding it to the device dictionary and device type.
Job is still failing with the same error.
Error log pasted below: https://pastebin.com/4WwttdgP
Please check.
Best Regards Pavan Kumar
On Tue, Jan 9, 2024 at 4:27 PM Milosz Wasilewski milosz.wasilewski@foundries.io wrote:
Hi Pawan,
This setting comes from device type. I guess I can also set it in the device dictionary. Quick grep through LAVA sources shows this: {% set uboot_extra_error_message = 'Invalid partition' %} https://gitlab.com/search?group_id=6533952&repository_ref=master&sco...
As one of the examples shows, you can also set this as job context:
context: uboot_extra_error_message: "Invalid partition"
https://gitlab.com/lava/functional-tests/-/blob/master/release/x15-extended....
Hope this helps.
Best Regards, Milosz
On Tue, Jan 9, 2024 at 10:05 AM pawanKumar pawan4749@gmail.com wrote:
Hello Team,
I was trying to flash a binary on the device and run the tests on the device by using lava overlay. Board flashes successfully but while booting the device in the boot log there is a word "** Invalid partition 3 **" lava catches the key word and throws an error message. For the other devices it is not catching this error with the same boot log. Only on one device I'm observing this issue.
Please let me know How to ignore the keyword and move on to run the tests.
matched a bootloader error message: 'Invalid partition' (17) boot log: U-Boot SPL 2022.04 (Nov 30 2023 - 20:10:15 +0000) power_bd71837_init DDRINFO: start DRAM init DDRINFO: DRAM rate 1600MTS DDRINFO:ddrphy calibration done DDRINFO: ddrmix config done Normal Boot Trying to boot from MMC1 hab fuse not enabled Authenticate image from DDR location 0x401fcdc0... NOTICE: BL31: v2.6(release):lf-5.15.32-2.0.0-0-gc6a19b1a3-dirty NOTICE: BL31: Built : 06:37:22, Jun 7 2022 U-Boot 2022.04 (Nov 30 2023 - 20:10:15 +0000) CPU: i.MX8MMD rev1.0 1600 MHz (running at 1200 MHz) CPU: Industrial temperature grade (-40C to 105C) at 44C Reset cause: POR Model: DRAM: 224 MiB board_init Core: 61 devices, 21 uclasses, devicetree: separate MMC: FSL_SDHC: 0 Loading Environment from nowhere... OK In: serial Out: serial Err: serial SEC0: RNG instantiated BuildInfo:
- ATF c6a19b1
facmod value is 1! pulse number is 0�flash target is MMC:0 Fastboot: Normal Normal Boot
Hit any key to stop autoboot: 2 end: 3.4.2 bootloader-interrupt (duration 00:00:05) [common] start: 3.4.3 bootloader-commands (timeout 00:02:52) [common] Setting prompt string to ['=>'] bootloader-commands: Wait for prompt ['=>'] (timeout 00:02:52) 0 Setting prompt string to ['=>'] Sending with 5 millisecond of delay setenv factorymode 1 u-boot=> setenv factorymode 1 bootloader-commands: Wait for prompt ['=>'] (timeout 00:02:51) setenv factorymode 1 Sending with 5 millisecond of delay boot u-boot=> boot
boot ** Invalid partition 3 ** Couldn't find partition mmc 0:3 Can't set block device uEnv not found in mmcpart3, checking mmcpart1 Failed to load '/boot/system/uEnv' uEnv not found in mmcpart 1 either! Booting from mmc ... ## Error: "w" not defined matched a bootloader error message: 'Invalid partition' (17) end: 3.4.3 bootloader-commands (duration 00:00:02) [common] case: bootloader-commands case_id: 204071 definition: lava duration: 1.52 extra: ... level: 3.4.3 namespace: common result: fail
Best Regards Pavan Kumar _______________________________________________ lava-devel mailing list -- lava-devel@lists.lavasoftware.org To unsubscribe send an email to lava-devel-leave@lists.lavasoftware.org