From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <HimaniRamesh.Barde@windriver.com>,
<openembedded-core@lists.openembedded.org>
Cc: <mathieu.dubois-briand@bootlin.com>,
<jose.quaresma@oss.qualcomm.com>, <Randy.MacLeod@windriver.com>,
<ross.burton@arm.com>, <raj.khem@gmail.com>,
<richard.purdie@linuxfoundation.org>,
<Shiva.Komati@windriver.com>
Subject: Re: [OE-core][PATCH v4] systemd: re-enable ptest support
Date: Wed, 16 Sep 2026 13:48:55 +0200 [thread overview]
Message-ID: <DLGPU9H3OWC3.O9CIGBIM0C0G@bootlin.com> (raw)
In-Reply-To: <20260909085518.640950-1-HimaniRamesh.Barde@windriver.com>
Hi,
On Wed Sep 9, 2026 at 10:55 AM CEST, Himani Ramesh Barde via lists.openembedded.org wrote:
> ptest support for systemd was dropped in 2018 (commit 906230a73b3c)
> when the recipe switched to meson, as there was no easy way to install
> and run the test suite. Current systemd and meson resolve this: the
> meson 'install-tests' option installs the unit-test binaries and a
> run-unit-tests.py runner under ${prefix}/lib/systemd/tests, and
> run-unit-tests.py already emits PASS:/SKIP: results per test.
>
> Add a 'tests' PACKAGECONFIG gated on PTEST_ENABLED that sets -Dtests
> and -Dinstall-tests and pulls in python3-pefile-native (needed to build
> the boot hwids test). do_install_ptest relocates the installed tests
> into ${PTEST_PATH} and drops the mkosi/integration-tests harness (which
> needs a booted system). A run-ptest wrapper drives run-unit-tests.py,
> and systemd is registered in ptest-packagelists.inc.
>
> The test/units integration tests, which require a booted system, are
> out of scope here and can be addressed separately.
>
> Verified on oe-core master (261.2, qemux86-64): with ptest enabled, 342
> unit-test binaries plus run-unit-tests.py install into ${PTEST_PATH} and
> systemd-ptest packages cleanly with no QA errors.
>
> [YOCTO #16386]
I think this is triggering the following error on our test infra:
Parsing recipes...ERROR: /srv/pokybuild/yocto-worker/check-layer/build/layers/openembedded-core/meta/recipes-core/systemd/systemd_261.3.bb: QA Issue: Package systemd-ptest is skipping required QA tests. [debug-files]
ERROR: /srv/pokybuild/yocto-worker/check-layer/build/layers/openembedded-core/meta/recipes-core/systemd/systemd_261.3.bb: Fatal QA errors were found, failing task.
Full log: https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/8951661/raw_inline
Parent build: https://autobuilder.yoctoproject.org/valkyrie/#/builders/27/builds/4717
This is happening when checking the meta-mingw layer with check-layer though…
Do you mind looking into it?
Thanks,
Antonin
prev parent reply other threads:[~2026-09-16 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 8:55 [OE-core][PATCH v4] systemd: re-enable ptest support Himani Ramesh Barde
2026-09-15 8:17 ` Jose Quaresma
2026-09-16 11:48 ` Antonin Godard [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=DLGPU9H3OWC3.O9CIGBIM0C0G@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=HimaniRamesh.Barde@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Shiva.Komati@windriver.com \
--cc=jose.quaresma@oss.qualcomm.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.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