Re: [PATCH v6 00/10] Add SBOM generation with debsbom

[Zhihang Wei <wzh@ilbers.de>]

On 12/9/25 15:49, MOESSBAUER, Felix wrote:
> On Tue, 2025-12-09 at 15:21 +0100, Zhihang Wei wrote:
>> Hi,
>> There are mulltiple test cases failed on CI.
> Hi,
>
> that's very unfortunate. As I'm not able to run the CI, for me it is
> basically impossible to catch these corner cases (especially the ones
> in the isar-image-ci, which is somewhat special). This topic also has
> been extensively discussed at the isar community meetup and identified
> as a major blocker for contributions.
>
> To move forward, we need a different strategy:
>
> Patches 1-5 are probably not breaking things. Please consider a partial
> apply of the series. The series is written in a way that it can be
> applied linearly.
I'll put p1-5 on CI and get back to you tomorrow.

Zhihang
> We need a way to get quick feedback regarding which CI tests break.
> With these one-per-week feedback rounds where other patches are applied
> in-between, I don't see a chance of getting the sbom feature integrated
> at all.
>
> Finally, we need to reduce the runtime of the testsuite and make it
> possible to easily execute just the failed tests. The testsuite wrapper
> script from Cedric could help in this regard.
>
>>
>> On fast CI:
>>
>> Failed test case: citest.py:DevTest.test_dev
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_5b_fast/4/build/tmp/work/debian-bookworm-amd64/isar-image-ci-qemuamd64/1.0-r0/temp/log.do_image_wic.3897481
>> dpkg-query: no packages found matching systemd-boot-efi:amd64
>>
>> Failed test case: citest.py:DevTest.test_dev_apps
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_5b_fast/4/build/tmp/work/debian-bookworm-amd64/isar-image-ci-qemuamd64/1.0-r0/temp/log.do_image_wic.18529
>> dpkg-query: no packages found matching systemd-boot-efi:amd64
>>
>> Failed test case: citest.py:DevTest.test_dev_rebuild
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_5b_fast/4/build/tmp/work/debian-bookworm-amd64/isar-image-ci-qemuamd64/1.0-r0/temp/log.do_image_wic.262594
>> dpkg-query: no packages found matching systemd-boot-efi:amd64
>>
>> Failed test case: citest.py:CrossTest.test_cross_debsrc
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_5b_fast/4/build/tmp/work/debian-bookworm-arm64/isar-image-ci-qemuarm64/1.0-r0/temp/log.do_image_wic.3057235
>> dpkg-query: no packages found matching systemd-boot-efi:arm64
>>
>> Failed test case: citest.py:CrossTest.test_cross_dependencies
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_5b_fast/4/build/tmp/work/debian-bookworm-arm64/isar-image-ci-qemuarm64/1.0-r0/temp/log.do_image_wic.772494
>> dpkg-query: no packages found matching systemd-boot-efi:arm64
> This class of failures seems to be related to the anti-pattern of
> overwriting machine configs in an image recipe. I'll work on a fix.
>
>>
>> On full CI:
>>
>> Failed test case: citest.py:ReproTest.test_repro_unsigned:
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_7b/28/build/tmp/work/debian-bookworm-amd64/isar-image-base-qemuamd64/1.0-r0/temp/log.do_image_wic.862703
>> bwrap: Can't mkdir /mnt/rootfs: Permission denied
>> I assume this is related with CI environment. This error is also there
>> for v5.
> Possible. I never saw it before.
>
>> Failed test case: citest.py:InstallerTest.test_installer_build:
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_7b/28/build/tmp/work/debian-bookworm-amd64/isar-image-ci-qemuamd64/1.0-r0/temp/log.do_image_wic.1240668
>> dpkg-query: no packages found matching systemd-boot-efi:amd64
>>
>> Failed test case: citest.py:KernelTests.test_per_kernel:
>> Logfile of failure stored in:
>> /build/isar_wzh_devel_7b/28/build/tmp/work/debian-bookworm-arm64/isar-image-ci-qemuarm64/1.0-r0/temp/log.do_image_wic.1626092
>> dpkg-query: no packages found matching systemd-boot-efi:arm64
>>
>> Failed test case: citest.py:InitRdTest.test_dracut_in_image:
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_7b/28/build/tmp/work/debian-bookworm-amd64/isar-image-ci-qemuamd64/1.0-r0/temp/log.do_image_wic.1723289
>> dpkg-query: no packages found matching systemd-boot-efi:amd64
>>
>> Failed test case: citest.py:InitRdCrossTests.test_dracut_in_image:
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_7b/28/build/tmp/work/debian-bookworm-amd64/isar-image-ci-qemuamd64/1.0-r0/temp/log.do_image_wic.2466233
>> dpkg-query: no packages found matching systemd-boot-efi:amd64
>>
>> Failed test case: citest.py:WicTest.test_wic_nodeploy_partitions:
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_7b/28/build/tmp/work/debian-bookworm-arm64/isar-image-ci-qemuarm64/1.0-r0/temp/log.do_image_wic.2823952
>> dpkg-query: no packages found matching systemd-boot-efi:arm64
>>
>> Failed test case: citest.py:WicTest.test_wic_deploy_partitions:
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_7b/28/build/tmp/work/debian-bookworm-arm64/isar-image-ci-qemuarm64/1.0-r0/temp/log.do_image_wic.2892279
>> dpkg-query: no packages found matching systemd-boot-efi:arm64
>>
>> 07:06:42
>> 18-/build/isar_wzh_devel_7b/28/testsuite/citest.py:NoCrossTest.test_nocross:
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_7b/28/build/tmp/work/debian-bookworm-amd64/isar-image-ci-qemuamd64-iso/1.0-r0/temp/log.do_image_squashfs.1864458
>> dpkg-query: no packages found matching systemd-boot-efi:amd64
>>
>> Failed test case: citest.py:SstateTest.test_sstate_populate:
>> ERROR: Logfile of failure stored in:
>> /build/isar_wzh_devel_7b/28/build-sstate/tmp/work/debian-bullseye-amd64/isar-image-base-qemuamd64/1.0-r0/temp/log.do_image_wic.1858017
>> bwrap: Can't find source path
>> /build/isar_wzh_devel_7b/28/build-sstate/tmp/deploy/sbom/sbom-chroot: No
>> such file or directory
> On bullseye there should not be any sbom-chroot. I'm wondering why it
> even is executed. Investigating...
>
> Felix
>

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/3d97daa0-1ca2-410c-aa69-2dbaf92c7733%40ilbers.de.