Re: [yocto-autobuilder-helper][PATCH 09/11] config.json: add vcontainer-tests, vdkr-tests, vpdmn-tests jobs

Tim Orling <[email protected]> Mon, 11 May 2026 10:52:16 -0700
Newsgroups org.yoctoproject.lists.yocto,org.yoctoproject.lists.yocto-patches
Message-ID <CAOyo-87A4t+VFHg3iwOf7pk0W7et4YZJ-=1O8CqM72xc7iTNBg@mail.gmail.com>
On Mon, May 11, 2026 at 1:57 AM Paul Barker <[email protected]> wrote:

> On Thu, 2026-05-07 at 18:25 -0700, [email protected] wrote:
> > From: Tim Orling <[email protected]>
> >
> > Add three pytest job overrides that run the meta-virtualization test
> > suites against the vcontainer standalone SDK published by the
> > vcontainer-tarball builder.
>
> I think this would be better as one job with three steps.
>
>
I considered that. No strong arguments either way.


> >
> > Each job runs the new scripts/run-vcontainer-tests helper via
> > EXTRACMDS (we need BUILDDIR variable so EXTRAPLAINCMDS is not
> > sufficient) with both NOBUILDTOOLS and NOVCONTAINER set, so the
> > workers don't spend time setting up either tarball: the test runner
> > gets the published SDK installer through VCONTAINER_SDK and manages
> > its own pytest venv.
> >
> > vcontainer-tests covers the broader bbclass/tooling tests (and so
> > brings in meta-openembedded layers it transitively exercises);
> > vdkr-tests and vpdmn-tests cover their respective CLI harnesses.
> >
> > AI-Generated: Claude Cowork Opus 4.7
> > Signed-off-by: Tim Orling <[email protected]>
> > ---
> >  config.json                  | 42 +++++++++++++++++++++++++++++++++++-
> >  scripts/run-vcontainer-tests |  7 +++---
> >  2 files changed, 44 insertions(+), 5 deletions(-)
> >
> > diff --git a/config.json b/config.json
> > index 86c1ffb..dda5b12 100644
> > --- a/config.json
> > +++ b/config.json
> > @@ -1891,7 +1891,7 @@
> >              },
> >              "step2" : {
> >                  "shortname" : "Publish vcontainer SDK for test reuse",
> > -                "EXTRAPLAINCMDS" : [
> > +                "EXTRACMDS" : [
>
> This fixup should be squashed into the earlier patch in this series that
> added this line.
>
>
Agreed. Oversight. I'll fix it in V2.


> [snip]
>
> > diff --git a/scripts/run-vcontainer-tests b/scripts/run-vcontainer-tests
> > index cbb5544..1394c7c 100755
> > --- a/scripts/run-vcontainer-tests
> > +++ b/scripts/run-vcontainer-tests
> > @@ -3,7 +3,7 @@
> >  # SPDX-License-Identifier: GPL-2.0-only
> >  #
> >  # Run meta-virtualization pytest test suites against the vcontainer
> > -# standalone SDK (vdkr/vpdmn) that was built by the previous bitbake
> > +# standalone SDK (vdkr/vpdmn) that was built in a previous bitbake
> >  # step.
> >  #
> >  # Arguments:
> > @@ -21,9 +21,8 @@
> >  #
> >  # The script is intentionally conservative: any pytest tests that
> cannot run
> >  # in the CI environment (those marked "slow", "network", "boot") are
> skipped
> > -# are skipped so that the autobuilder step completes without needing
> network
> > -# access. Those can be re-enabled by exporting META_VIRT_PYTEST_MARKERS
> > -# before invocation.
> > +# so that the autobuilder step completes without needing network
> access. Those
> > +# can be re-enabled by exporting META_VIRT_PYTEST_MARKERS before
> invocation.
> >  #
> >  # It is assumed that /dev/kvm is writable by the CI user running the
> tests,
> >  # since the performance is significantly faster with 'memres'.
>
> As above, these fixups need squashing into the patch that added
> run-vcontainer-tests.
>
>
Agreed. Oversight. I'll fix it in V2.



> Best regards,
>
> --
> Paul Barker
>
>