cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc baseline-nfs: 18 runs, 1 regressions (v5.10.100-cip2-425-g0a0d92194f39) Regressions Summary ------------------- platform | arch | lab |

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc baseline-cip-nfs: 9 runs, 1 regressions (v5.10.100-cip2-425-g0a0d92194f39) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc baseline: 89 runs, 1 regressions (v5.10.100-cip2-425-g0a0d92194f39) Regressions Summary ------------------- platform | arch | lab |

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc build: 175 builds: 3 failed, 172 passed, 4 errors, 9 warnings (v5.10.100-cip2-425-g0a0d92194f39) Full Build Summary:

cip-gitlab/ci/iwamatsu/linux-4.19.y-cip-rc build: 192 builds: 6 failed, 186 passed, 2 errors, 32 warnings (v4.19.231-cip68-89-gd39fc5cc85ff) Full Build Summary:

Please give kas 3.0.2 now a try. It should finally work without undesired side-effects. Thanks, Jan -- Siemens AG, Technology Competence Center Embedded Linux

Hello Iwamatsu-san, all, I've started to add v4.9.y-rc testing support. Initially the build/test support [0] is identical to our v4.4.y-rc testing [1]. In a test run [2] however, we're seeing three

Thanks for taking care! Applied to next. Jan -- Siemens AG, Technology Competence Center Embedded Linux

From: Srinuvasan A <srinuvasan_a@...> Bump kernel versions for linux-cip-kernel 4.4,4.19 and 5.10. Signed-off-by: Srinuvasan A <srinuvasan_a@...> --- ...4.4.285-cip63-rt36.bb =>

cip-gitlab/ci/pavel/linux-test build: 155 builds: 3 failed, 152 passed, 4 errors, 9 warnings (v5.10.100-cip2-319-g7182f5032311) Full Build Summary:

That warning is just a cosmetic issue, but I plan to fix it with 3.0.1 this week. The actual issue was (now fixed in next) that swupdate images did not build. CI would have revealed it as well, but I

This also resolves the build breakage we see with bullseye-based kas-iser:3.0 which no longer carried fdisk (which it did by chance so far). Out of curiosity: gz is not a particularly recent method

From: Quirin Gylstorff <quirin.gylstorff@...> Newer versions of the wic provide separated disk partitions therefore, the extraction code is no longer necessary. Rename the class from

I did a build and verified the pipeline in KAS github, It seems okay, but when i trigger the build i was able to see some logs related to sbuildAdding user `builder' to group `sbuild' ... Adding user

Please test before you submit: We have an open issue with kas-isar:3.0. Jan -- Siemens AG, Technology Competence Center Embedded Linux

From: Srinuvasan A <srinuvasan_a@...> Update to kas 3.0. Signed-off-by: Srinuvasan A <srinuvasan_a@...> --- .gitlab-ci.yml | 2 +- README.md | 2 +- 2 files changed, 2

From: Jan Kiszka <jan.kiszka@...> Move QEMU_EXTRA_ARGS into QEMU_COMMON_OPTIONS to unify the invocations. Signed-off-by: Jan Kiszka <jan.kiszka@...> --- start-qemu.sh | 17

Thanks, applied. Further cleanup on top will follow. Jan -- Siemens AG, Technology Competence Center Embedded Linux

From: Srinuvasan A <srinuvasan_a@...> Broke the normal boot part. Fixed them. -append takes arguments inside double quotes(""). If we escape and pass the " along with the value the final

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc ltp-timers: 9 runs, 2 regressions (v5.10.100-cip2-319-gcbff87047566) Regressions Summary ------------------- platform | arch | lab |