From: Zhihang Wei <wzh@ilbers.de>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"amikan@ilbers.de" <amikan@ilbers.de>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "ibr@ilbers.de" <ibr@ilbers.de>,
"Hombourger, Cedric" <cedric.hombourger@siemens.com>
Subject: Re: [PATCH v2 00/17] Various improvements to the testsuite
Date: Wed, 21 Jan 2026 16:43:06 +0100 [thread overview]
Message-ID: <c4f3b30c-0a0a-4146-ac52-d038ef7f906e@ilbers.de> (raw)
In-Reply-To: <5dade711-11fb-4b3f-be13-15f225373a3f@ilbers.de>
On 1/13/26 11:34, Zhihang Wei wrote:
>
> On 1/12/26 09:37, 'MOESSBAUER, Felix' via isar-users wrote:
>> On Fri, 2026-01-09 at 17:25 +0200, Anton Mikanovich wrote:
>>> 08/01/2026 16:37, Anton Mikanovich wrote:
>>>> Hello Felix,
>>>>
>>>> BTW you can look into full CI errors and logs of v2 patchset in build
>>>> artifacts
>>>> on our Gitlab:
>>>>
>>>> https://gitlab.isar-build.org/ilbers/isar/-/jobs/2686
>>>>
>>>> I also have the first version of startvm "reorder" fix currently
>>>> tested
>>>> (on top of v2, rebased on next). Results will be available here:
>>>>
>>>> https://gitlab.isar-build.org/ilbers/isar/-/jobs/2704
>>> Hello Felix,
>>>
>>> Unfortunately this job was failed due to network issue, but there
>>> was also
>>> strange issue on SstateTest.test_sstate_populate testcase:
>>>
>>> Running 'git --work-tree=/builds/ilbers/isar/isar-sstate checkout
>>> HEAD -- .'
>>> [stderr] fatal: detected dubious ownership in repository at
>>> '/builds/ilbers/isar'
>>>
>>> Not sure why it happened, while fetching code wasn't changed.
>> This is a git hardening, which came in with kas 4.8, fixed in 4.8.2
>> [1].
>>
>> As we don't execute the testsuite using kas itself, but only as part of
>> the kas container this hardening needs to be lessened. Either use kas
>> 4.8.2 or 5.x.
>>
>> [1]
>> https://github.com/siemens/kas/commit/733643709e7e25723a75ad2a81c32942f660436b
>>
> Hi,
>
> I have updated to kas 4.8.2 on GitLab, another issue has appeared in the
> testcase SstateTest.test_sstate_populate. Log follows:
>
> INFO: Creating image(s)...
>
> Traceback (most recent call last):
> File "/build/isar_wzh_devel_6b/15/isar-sstate/scripts/wic", line
> 547, in <module>
> sys.exit(main(sys.argv[1:]))
> File "/build/isar_wzh_devel_6b/15/isar-sstate/scripts/wic", line
> 542, in main
> return hlp.invoke_subcommand(args, parser, hlp.wic_help_usage,
> subcommands)
> File
> "/build/isar_wzh_devel_6b/15/isar-sstate/scripts/lib/wic/help.py",
> line 83, in invoke_subcommand
> subcmd[0](args, usage)
> File "/build/isar_wzh_devel_6b/15/isar-sstate/scripts/wic", line
> 222, in wic_create_subcommand
> engine.wic_create(wks_file, rootfs_dir, bootimg_dir, kernel_dir,
> File
> "/build/isar_wzh_devel_6b/15/isar-sstate/scripts/lib/wic/engine.py",
> line 183, in wic_create
> plugin_class = PluginMgr.get_plugins('imager').get(pname)
> File
> "/build/isar_wzh_devel_6b/15/isar-sstate/scripts/lib/wic/pluginbase.py",
> line 61, in get_plugins
> spec.loader.exec_module(module)
> File "<frozen importlib._bootstrap_external>", line 790, in exec_module
> File "<frozen importlib._bootstrap>", line 228, in
> _call_with_frames_removed
> File
> "/build/isar_wzh_devel_6b/15/isar-sstate/scripts/lib/wic/plugins/imager/direct.py",
> line 22, in <module>
> from oe.path import copyhardlinktree
> ModuleNotFoundError: No module named 'oe'
>
> [stdlog] 2026-01-13 06:08:32,821 avocado.test cibuilder L0345 INFO |
> NOTE: recipe isar-image-base-1.0-r0: task do_image_wic: Failed
>
>
> You can look into the full log of this issue on GitLab:
> https://gitlab.isar-build.org/ilbers/isar/-/pipelines/2602
>
>
> I have verified this error can be reproduced locally:
> 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:SstateTest.test_sstate_populate$
>
> I'll look into this specific issue at the moment.
>
> Zhihang
Now I see the issue is caused by p11 of this patch set. This test case
SstateTest.test_sstate_populate checks out another copy of isar inside
isar-sstate. Paths like "${TOPDIR}/../meta" were not mounted correctly,
so the
python module cannot be found.
I just don't have an idea on how to fix this issue to keep both this
test case
and SignatureTest working at the same time.
Zhihang
>>> Anyway I've rebased the branch (and added one fix for container startvm
>>> test),
>>> and prebuilt_containers startvm tests are still failing. Will look into
>>> it when
>>> the job will be finished:
>>>
>>> https://gitlab.isar-build.org/ilbers/isar/-/jobs/2710
>> This is strange, as I'm able to execute just the prebuilt_containers
>> without executing any other tests in advance (du to the controversial
>> build-before-run added to these tests).
>>
>>
>>> Sstatecache tests are executed in the end, so we will see if they also
>>> fail on
>>> git checkout.
>> I'm also wondering why the NoCrossTest.test_run_arm_trixie fails.
>> But in general it doesn't look too bad. Hopefully we can sort the
>> remaining issues out and merge this to finally move forward with the
>> missing features of the SBOM series.
>>
>> 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/c4f3b30c-0a0a-4146-ac52-d038ef7f906e%40ilbers.de.
next prev parent reply other threads:[~2026-01-21 15:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 13:19 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 01/17] testsuite: move targets with custom kernel to separate test 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 02/17] testsuite: enable ccache on kernel tests 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 03/17] testsuite: make prebuilt container a feature test 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 04/17] testsuite: make compat test standalone test 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 05/17] testsuite: handle IMAGE_INSTALL solely in cibuilder.py 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 06/17] testsuite: limit cross_debsrc test to subset of packages 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 07/17] testsuite: forward SSTATE_MIRRORS into CI env on sstate 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 08/17] ci: add support for sstate cache 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 09/17] testsuite: make test_cross_deps more specific 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 10/17] testsuite: fix typo in log message in perform_signature_lint 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 11/17] testsuite: fix SignatureTest by avoiding absolute path in bblayers 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 12/17] testsuite: use more recent distros in SignatureTest 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 13/17] testsuite: make SignatureTest idempotent 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 14/17] testsuite: add rootfs target for rootfs only tests 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 15/17] testsuite: refactor sbom tests to avoid overhead 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 16/17] testsuite: make sbuild-flavor test standalone 'Felix Moessbauer' via isar-users
2025-12-19 13:19 ` [PATCH v2 17/17] testsuite: skip VM tests if images are not available 'Felix Moessbauer' via isar-users
2026-01-07 11:59 ` [PATCH v2 00/17] Various improvements to the testsuite 'MOESSBAUER, Felix' via isar-users
2026-01-07 12:33 ` Anton Mikanovich
2026-01-07 13:13 ` 'MOESSBAUER, Felix' via isar-users
2026-01-07 13:48 ` Anton Mikanovich
2026-01-07 13:55 ` 'MOESSBAUER, Felix' via isar-users
2026-01-07 14:09 ` Baurzhan Ismagulov
2026-01-07 15:03 ` Anton Mikanovich
2026-01-08 14:37 ` Anton Mikanovich
2026-01-09 15:25 ` Anton Mikanovich
2026-01-12 8:37 ` 'MOESSBAUER, Felix' via isar-users
2026-01-13 10:34 ` Zhihang Wei
2026-01-21 15:43 ` Zhihang Wei [this message]
2026-01-21 16:07 ` 'MOESSBAUER, Felix' 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=c4f3b30c-0a0a-4146-ac52-d038ef7f906e@ilbers.de \
--to=wzh@ilbers.de \
--cc=amikan@ilbers.de \
--cc=cedric.hombourger@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.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