public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com
Subject: Re: [PATCH 0/2] Make SBOM naming more robust against downstream changes
Date: Fri, 27 Mar 2026 12:13:16 +0100	[thread overview]
Message-ID: <7b6e181d-9ae1-4634-9b14-d9b51d878caf@ilbers.de> (raw)
In-Reply-To: <20260326082015.3169480-1-felix.moessbauer@siemens.com>



On 3/26/26 09:20, 'Felix Moessbauer' via isar-users wrote:
> This series goes on top of: merge_wic_sbom: fix merging of multiple SBOMs,
> but is otherwise independent.
>
> The related inconsistencies have been found on isar-cip-core tests
> (kas-cip.yml:kas/board/x86-uefi.yml:kas/opt/rt.yml:kas/opt/test.yml:kas/opt/trixie.yml)
> where the IMAGE_FULLNAME variable is changed and no longer equal to
> ROOTFS_PACKAGE_SUFFIX. Without the patches, the respective CIP variant cannot be built.
>
> PS: would it be possible to have an isar release candidate, to encourage
> more downstream layers to start testing?
I'll get back to you later on this.
> Best regards,
> Felix
>
> Felix Moessbauer (2):
>    sbom: derive rootfs sbom name from ROOTFS_PACKAGE_SUFFIX
>    sbom: use ROOTFS_PACKAGE_SUFFIX on merging
>
>   meta/classes-recipe/imagetypes_wic.bbclass | 2 +-
>   meta/classes/sbom.bbclass                  | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
>
Failed on fast CI "citest.py:SbomTest.test_sbom_rootfs_generate":

|[stdlog] 2026-03-27 11:46:36,083 avocado.test cibuilder L0345 INFO | 
NOTE: Tasks Summary: Attempted 486 tasks of which 0 didn't need to be 
rerun and all succeeded. [stdlog] 2026-03-27 11:46:37,373 BitBake main 
L0465 INFO | Starting bitbake server... [stdlog] 2026-03-27 11:46:40,159 
avocado.test cibase L0162 INFO | Check cdx SBOM in 
/build/isar_wzh_devel_1z_others/15/build/tmp/deploy/images/qemuamd64/isar-rootfs-ci-debian-bookworm-qemuamd64.cdx.json 
[stdlog] 2026-03-27 11:46:40,159 avocado.test stacktrace L0040 ERROR| 
[stdlog] 2026-03-27 11:46:40,159 avocado.test stacktrace L0042 ERROR| 
Reproduced traceback from: 
/tmp/avocado_venv/lib/python3.11/site-packages/avocado/core/test.py:638 
[stdlog] 2026-03-27 11:46:40,159 avocado.test stacktrace L0049 ERROR| 
Traceback (most recent call last): [stdlog] 2026-03-27 11:46:40,159 
avocado.test stacktrace L0049 ERROR| File 
"/build/isar_wzh_devel_1z_others/15/testsuite/citest.py", line 1092, in 
test_sbom_rootfs_generate [stdlog] 2026-03-27 11:46:40,159 avocado.test 
stacktrace L0049 ERROR| self.perform_sbom_test(targets) [stdlog] 
2026-03-27 11:46:40,159 avocado.test stacktrace L0049 ERROR| File 
"/build/isar_wzh_devel_1z_others/15/testsuite/cibase.py", line 163, in 
perform_sbom_test [stdlog] 2026-03-27 11:46:40,159 avocado.test 
stacktrace L0049 ERROR| with open(sbom_path) as f: [stdlog] 2026-03-27 
11:46:40,160 avocado.test stacktrace L0049 ERROR| ^^^^^^^^^^^^^^^ 
[stdlog] 2026-03-27 11:46:40,160 avocado.test stacktrace L0049 ERROR| 
FileNotFoundError: [Errno 2] No such file or directory: 
'/build/isar_wzh_devel_1z_others/15/build/tmp/deploy/images/qemuamd64/isar-rootfs-ci-debian-bookworm-qemuamd64.cdx.json'|

To redo the test on your machine using avocado:
1. Have a clean clone of isar, checkout to branch next and apply your 
patches:
$ git clone -b next https://github.com/ilbers/isar.git
$ cd isar
$ git am /path-to/0001-my-contribution-to-isar.patch
2. Run kas shell, setup CI prerequisites (avocado, qemu) and cleanup:
$ ./kas/kas-container shell kas/isar.yaml --command \
     "rm -rf /work/build/conf && /work/scripts/ci_setup.sh"
3. Run the failed test:
$ cd /work/testsuite
$ avocado run citest.py:SbomTest.test_sbom_rootfs_generate

Zhihang


-- 
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/7b6e181d-9ae1-4634-9b14-d9b51d878caf%40ilbers.de.

      parent reply	other threads:[~2026-03-27 11:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26  8:20 'Felix Moessbauer' via isar-users
2026-03-26  8:20 ` [PATCH 1/2] sbom: derive rootfs sbom name from ROOTFS_PACKAGE_SUFFIX 'Felix Moessbauer' via isar-users
2026-03-26  8:20 ` [PATCH 2/2] sbom: use ROOTFS_PACKAGE_SUFFIX on merging 'Felix Moessbauer' via isar-users
2026-03-27 11:13 ` Zhihang Wei [this message]

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=7b6e181d-9ae1-4634-9b14-d9b51d878caf@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    /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