cip-gitlab/ci/iwamatsu/linux-4.19.y-cip-rc ltp-pty: 4 runs, 4 regressions (v4.19.237-cip71-369-gd31a7c52552af) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-4.19.y-cip-rc baseline: 103 runs, 1 regressions (v4.19.237-cip71-369-gd31a7c52552af) Regressions Summary ------------------- platform | arch | lab |

cip-gitlab/ci/iwamatsu/linux-4.19.y-cip-rc baseline-nfs: 13 runs, 1 regressions (v4.19.237-cip71-369-gd31a7c52552af) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-4.19.y-cip-rc build: 197 builds: 6 failed, 191 passed, 2 errors, 32 warnings (v4.19.237-cip71-369-gd31a7c52552af) Full Build Summary:

From: Jan Kiszka <jan.kiszka@...> This is more logical because the rootfs is going to be overwritten completely on updates. Everything that is supposed to stay should go into the

Unifies secure and non-secure swupdate variants further by using a read-only rootfs in both cases. See patchs for more details. Applies on top of "SWUpdate & EFI Boot Guard refactorings". Jan Jan

From: Jan Kiszka <jan.kiszka@...> No need to run this for non-qemu and non-x86. And, yes, overrides can stack. Signed-off-by: Jan Kiszka <jan.kiszka@...> ---

From: Jan Kiszka <jan.kiszka@...> First, sda is the default anyway. But, more importantly, we do not need this parameter in these cases as we either mount by label/uuid or do not mount at all

From: Jan Kiszka <jan.kiszka@...> SQUASHFS_EXCLUDE_DIRS is given a default value in this class, so the 'or ""' is redundant. Furthermore, remove the unneeded space from

From: Jan Kiszka <jan.kiszka@...> VERITY_IMAGE_TYPE defines where the verity-img class takes its input from. Ensure that this class is present and hook it up directly in verity-img. Makes the

From: Quirin Gylstorff <quirin.gylstorff@...> If an image with a read-only partition and etc overlay is build journalctl does not display the system log in Debian Bullseye. The log is

Hi Chris, (and lab maintainers) I noticed that the labs other than lab-cip-cybertrust are offline now. I think lab reboots will be needed. https://lava.ciplatform.org/scheduler/allworkers Best

cip-gitlab/ci/iwamatsu/linux-4.19.y-cip-rc ltp-pty: 5 runs, 5 regressions (v4.19.237-cip71-337-g1c3cfbe23f3d7) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-4.19.y-cip-rc baseline: 112 runs, 5 regressions (v4.19.237-cip71-337-g1c3cfbe23f3d7) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-4.19.y-cip-rc baseline-nfs: 17 runs, 1 regressions (v4.19.237-cip71-337-g1c3cfbe23f3d7) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-4.19.y-cip-rc build: 198 builds: 6 failed, 192 passed, 2 errors, 32 warnings (v4.19.237-cip71-337-g1c3cfbe23f3d7) Full Build Summary:

Hi Pavel, I'm sorry for the inconvenience. The lab-cip-cybertrust was offline with an internal error. The lab is now online and running the submitted jobs in sequence. Best regards, Hiraku

From: Jan Kiszka <jan.kiszka@...> The python3-all dependency must be broken up into libpython3-all-dev and python3-all-dev:any so that other packages can still install native python into the

Hi! It seems that zynqmp has problems: https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/2336993733 Job #663506: Submitted 67Health: Unknown 68Device Type:

Not from me. either works for me. Thanks, Alicef -- ====================================== Cybertrust Japan Co.,Ltd. Alice