Hello,

as far as I remember, LAVA is using the python format function to replace the variables inside the commands.

So if you double the brackets that should work, like: "${{mfg_mmcdev}}p1"

Rgds

Le lun. 25 janv. 2021 à 10:48, Westermann, Oliver < Oliver.Westermann@cognex.com> a écrit :

Hey,

we recently updated our LAVA setup from 2020.06 to 2020.12. After a few hickups we’re back running, but we are greeted with a few new warnings:

Our setup uses the iMX8 and the UUU boot method, which uses several, internal variables. Internal = Internal to U-Boot or bash, for example:

...

FB: ucmd setenv fastboot_buffer ${loadaddr}

...

FBK: ucmd mkfs.ext4 -F -E nodiscard /dev/mmcblk${mfg_mmcdev}p1

With the recent LAVA version, this causes a warning:

{"dt": "2021-01-25T07:43:46.551216", "lvl": "warning", "msg": "Missing key : '{mfg_mmcdev}' for string 'ucmd mkfs.ext4 -F -E nodiscard /dev/mmcblk${mfg_mmcdev}p1'"}

While I could reduce this by removing the brackets in the first case, this won’t work for the second case.

Is there a way to provide eg a variable whitelist? The 30 warnings boil down to 4-5 variables, so this might be a useful feature addition.

Any other ideas of cause welcome, maybe I will try to use this for my first contribution here 😊

Best regards, Olli

---

Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users