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
Hello,
for information, the schema validator is already printing a warning when such parameter is present in the boot section.
Rgds
Le sam. 2 nov. 2019 à 19:39, Milosz Wasilewski milosz.wasilewski@linaro.org a écrit :
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
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
lava-users@lists.lavasoftware.org