Re: [PATCH v2 00/17] Various improvements to the testsuite

["'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>]

On Wed, 2026-01-21 at 16:43 +0100, Zhihang Wei wrote:
> 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.

Thanks for debugging this. I propose to just disable the SstateCache
test for now. This feature is used in daily builds and (in case we
decide to enable it in CI, as done in this series) also tested
transitively.

IMHO it is more important to speedup the CI and move on, than testing
this explicitly.

Felix

> 
> 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
> > > 
> > 

-- 
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/f8c2119334070723999d5ece7496cb521bab6259.camel%40siemens.com.