On Tue, Sep 8, 2026 at 8:00 AM Mathieu Dubois-Briand via
lists.openembedded.org <mathieu.dubois-briand=
[email protected]> wrote:

> 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 <[email protected]>
> >> ---
> >
> > 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


I believe this can be fixed in
meta/conf/distro/include/ptest-packagelists.inc with:
${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)}

Jose


>
>
> --
> Mathieu Dubois-Briand, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
> 
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#245334): 
https://lists.openembedded.org/g/openembedded-core/message/245334
Mute This Topic: https://lists.openembedded.org/mt/121127018/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to