All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <HimaniRamesh.Barde@windriver.com>,
	<openembedded-core@lists.openembedded.org>
Cc: <Randy.MacLeod@windriver.com>, <ross.burton@arm.com>,
	<jose.quaresma@oss.qualcomm.com>, <raj.khem@gmail.com>,
	<richard.purdie@linuxfoundation.org>,
	<Shiva.Komati@windriver.com>
Subject: Re: [OE-core][PATCH v3] systemd: re-enable ptest support
Date: Tue, 08 Sep 2026 09:00:27 +0200	[thread overview]
Message-ID: <DL9QP1CJD4I3.1CD0XIMDCNH2N@bootlin.com> (raw)
In-Reply-To: <DL9QO37EJTBL.1CBZPRPTN8QNP@bootlin.com>

On Tue Sep 8, 2026 at 8:59 AM CEST, Mathieu Dubois-Briand wrote:
> On Mon Sep 7, 2026 at 1:45 PM 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]
>>
>> Signed-off-by: Himani Ramesh Barde <HimaniRamesh.Barde@windriver.com>
>> ---
>
> Hi Himani Ramesh,
>
> This is failing on the autobuilder, as we are running ptests using the
> poky distro, but poky does not have systemd DISTRO_FEATURES. I'm not
> sure how we can fix this, but we might need to hack a bit.
>
> Do you know how it was working before it was dropped in 2018?
>
> Thanks,
> Mathieu

Sorry, I forgot to add the log:

ERROR: Nothing RPROVIDES 'systemd-ptest' (but virtual:mcextend:systemd:/srv/pokybuild/yocto-worker/qemuarm64-ptest/build/layers/openembedded-core/meta/recipes-core/images/core-image-ptest.bb RDEPENDS on or otherwise requires it)
systemd RPROVIDES systemd-ptest but was skipped: using DISTRO 'poky', which is missing required DISTRO_FEATURES: 'systemd usrmerge'
NOTE: Runtime target 'systemd-ptest' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['systemd-ptest']
NOTE: Runtime target 'core-image-ptest-all' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['core-image-ptest-all', 'core-image-ptest-systemd', 'systemd-ptest']
NOTE: Runtime target 'core-image-ptest-all-dev' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['core-image-ptest-all-dev', 'core-image-ptest-systemd', 'systemd-ptest']
ERROR: Nothing RPROVIDES 'core-image-ptest-systemd'
No eligible RPROVIDERs exist for 'core-image-ptest-systemd'
NOTE: Runtime target 'core-image-ptest-systemd' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['core-image-ptest-systemd']

https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/4482
https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/4509
https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/1157
https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/1137

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-09-08  7:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 11:45 [OE-core][PATCH v3] systemd: re-enable ptest support Himani Ramesh Barde
2026-09-08  6:59 ` Mathieu Dubois-Briand
2026-09-08  7:00   ` Mathieu Dubois-Briand [this message]
2026-09-08  7:39     ` Jose Quaresma
2026-09-08  7:46 ` Jose Quaresma

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=DL9QP1CJD4I3.1CD0XIMDCNH2N@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=HimaniRamesh.Barde@windriver.com \
    --cc=Randy.MacLeod@windriver.com \
    --cc=Shiva.Komati@windriver.com \
    --cc=jose.quaresma@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.