Re: [yocto-patches] [yocto-autobuilder-helper][PATCH v4 03/11] scripts: add run-vcontainer-tests for meta-virtualization

On Wed, Jul 15, 2026 at 12:09 PM Paul Barker via lists.yoctoproject.org
<[email protected]> wrote:

> On Mon, 2026-07-06 at 15:05 -0700, Tim Orling via lists.yoctoproject.org
> wrote:
> > Add scripts/run-vcontainer-tests, the test runner used by the
> > vcontainers-test job. It sources the vcontainer-tarball SDK,
> > discovers the meta-virtualization pytest suite, and runs a
> > configurable set of suites (vdkr, vpdmn, memres) against the
> > checked-out layers. Suites can be selected per-step so the
> > top-level 'vcontainer-tests' job runs the container engine
> > agnostic tests:
> >
> > - tests/test_container_cross_install.py
> > - tests/test_container_registry_script.py
> > - tests/test_vcontainer_auth_config.py
> > - tests/test_multiarch_oci.py
> > - tests/test_multilayer_oci.py
> >
> > The 'vdkr-tests' and 'vpdmn-tests' jobs run only their respective
> > suites (including memres for each container engine):
> >
> > - tests/test_vdkr.py
> > - tests/test_vdkr_registry.py
> >
> > and
> >
> > - tests/test_vpdmn.py
> >
> > The purpose of this script is to test the just built vcontainer-tarball,
> > so that it can be considered "known-good" and be published for use by
> > container building jobs that need the vcontainer-tarball installed.
> >
> > AI-Generated: Claude Cowork Opus 4.7
> > Signed-off-by: Tim Orling <[email protected]>
> > ---
> >  config.json                  |  31 +++++
> >  scripts/run-vcontainer-tests | 212 +++++++++++++++++++++++++++++++++++
> >  2 files changed, 243 insertions(+)
> >  create mode 100755 scripts/run-vcontainer-tests
> >
> > diff --git a/config.json b/config.json
> > index 972682d..ae13c5b 100644
>
<snip>

> >      },
>
> Hi Tim,
>
> Would it make sense to merge the vcontainer-tests steps in to the
> vcontainer-tarball job defined in patch 2 of this series? Essentially,
> build the tarball (step 1), test it (steps 2-4, merged from this patch),
> then publish it (step 5) only if it has passed the tests.
>

I contemplated that, but the tests were not passing [1][2][3] and I felt
it was out of scope for me to try to fix them now. If we can work with
Bruce to get the test cases to be more stable, this is a good idea for
the future.

In the earlier stages of this work, I relied on vcontainer-tarball
extensively since all containers were single-arch and pushing used
vdkr/vpdmn. Currently, on the AB, the use of the vcontainer-tarball is
for pushing single-arch containers (which is limited to the alpine
container ATM). When I figure out how to do run-time container
testing on the AB, that would be a second use case.

I was also not entirely sure how frequently we need/want to rebuild
the vcontainer-tarball (e.g. buildtools tarballs are not not published
frequently).

[1] https://autobuilder.yoctoproject.org/valkyrie/#/builders/118/builds/3
[2] https://autobuilder.yoctoproject.org/valkyrie/#/builders/118/builds/4
[3] https://autobuilder.yoctoproject.org/valkyrie/#/builders/118/builds/5


> Best regards,
>
> --
> Paul Barker
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#4481):
> https://lists.yoctoproject.org/g/yocto-patches/message/4481
> Mute This Topic: https://lists.yoctoproject.org/mt/120148311/924729
> Group Owner: [email protected]
> Unsubscribe:
> https://lists.yoctoproject.org/g/yocto-patches/leave/13169857/924729/1023951714/xyzzy
> [[email protected]]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
>