From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"wzh@ilbers.de" <wzh@ilbers.de>
Cc: "Steiger, Christoph" <christoph.steiger@siemens.com>,
"quirin.gylstorff@siemens.com" <quirin.gylstorff@siemens.com>,
"cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH v6 00/10] Add SBOM generation with debsbom
Date: Tue, 9 Dec 2025 14:49:19 +0000 [thread overview]
Message-ID: <67aa63be5b9a7fe41ce9fdf87cb9a76d8c538aff.camel@siemens.com> (raw)
In-Reply-To: <1d82fbfe-f625-45f6-bd6d-a0ad90845bab@ilbers.de>
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.
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
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
--
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/67aa63be5b9a7fe41ce9fdf87cb9a76d8c538aff.camel%40siemens.com.
next prev parent reply other threads:[~2025-12-09 14:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 8:58 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 01/10] refactor: move get_rootfs_distro from sdk into rootfs 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 02/10] meta: package python libraries for SBOM generation 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 03/10] meta: package python3-debsbom 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 04/10] meta: add SBOM generation with debsbom 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 05/10] override distro vendor in SBOM on Ubuntu 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 06/10] add support to add imager dependencies to BOM 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 07/10] wic: create uniform manifest describing all image components 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 08/10] qemuamd64: add IMAGER_BOM entries 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 09/10] imager: create SBOM of IMAGER_BOM packages 'Felix Moessbauer' via isar-users
2025-12-01 8:58 ` [PATCH v6 10/10] wic: create uniform SBOM describing all image components 'Felix Moessbauer' via isar-users
2025-12-01 9:15 ` [PATCH v6 00/10] Add SBOM generation with debsbom 'Jan Kiszka' via isar-users
2025-12-03 13:32 ` 'MOESSBAUER, Felix' via isar-users
2025-12-05 15:08 ` 'Bouska, Zdenek' via isar-users
2025-12-09 14:21 ` Zhihang Wei
2025-12-09 14:49 ` 'MOESSBAUER, Felix' via isar-users [this message]
2025-12-09 14:56 ` Zhihang Wei
2025-12-11 9:15 ` Zhihang Wei
2025-12-12 10:24 ` 'Jan Kiszka' via isar-users
2025-12-15 7:35 ` 'MOESSBAUER, Felix' via isar-users
2025-12-17 15:22 ` 'Jan Kiszka' via isar-users
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=67aa63be5b9a7fe41ce9fdf87cb9a76d8c538aff.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=cedric.hombourger@siemens.com \
--cc=christoph.steiger@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.com \
--cc=wzh@ilbers.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox