From: Paul Barker <paul@pbarker.dev>
To: uvv.mail@gmail.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v3 2/3] oe-selftest: overlayfs: Make the test more deterministic
Date: Thu, 15 Jan 2026 13:53:37 +0000 [thread overview]
Message-ID: <b06c5771c4f1405605db5aa21937a12d0ad73d2d.camel@pbarker.dev> (raw)
In-Reply-To: <20260114185508.380709-3-uvv.mail@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2316 bytes --]
On Wed, 2026-01-14 at 18:54 +0000, Vyacheslav Yurkov via
lists.openembedded.org wrote:
> From: Vyacheslav Yurkov <uvv.mail@gmail.com>
>
> The test orignally was written under assumption that poky distro is
> used. When poky-altcft is used for example, then systemd is already set
> in DISTRO_FETURES, which the test did not expect.
Hi,
The commit title here still talks about determinism. The test case was
deterministic though - previously it would always fail if systemd was
already in DISTRO_FEATURES. I think I misunderstood a little last time,
but this still needs renaming.
I also wonder why we're testing this here. Perhaps this can be turned
into a more generic test that REQUIRED_DISTRO_FEATURES behaves as
expected - we can use the overlayfs bbclass as part of that as we know
it sets REQUIRED_DISTRO_FEATURES.
>
> Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com>
> ---
> meta/lib/oeqa/selftest/cases/overlayfs.py | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/meta/lib/oeqa/selftest/cases/overlayfs.py b/meta/lib/oeqa/selftest/cases/overlayfs.py
> index 580fbdcb9c..3e55e97927 100644
> --- a/meta/lib/oeqa/selftest/cases/overlayfs.py
> +++ b/meta/lib/oeqa/selftest/cases/overlayfs.py
> @@ -5,7 +5,7 @@
> #
>
> from oeqa.selftest.case import OESelftestTestCase
> -from oeqa.utils.commands import bitbake, runqemu, get_bb_vars
> +from oeqa.utils.commands import bitbake, runqemu, get_bb_vars, get_bb_var
> from oeqa.core.decorator import OETestTag
> from oeqa.core.decorator.data import skipIfNotMachine
>
> @@ -46,7 +46,8 @@ inherit overlayfs
> res = bitbake('core-image-minimal', ignore_status=True)
> line = getline(res, "overlayfs-user was skipped: missing required distro features")
> self.assertTrue("overlayfs" in res.output, msg=res.output)
> - self.assertTrue("systemd" in res.output, msg=res.output)
> + if not "systemd" in get_bb_var('DISTRO_FEATURES'):
> + self.assertTrue("systemd" in res.output, msg=res.output)
> self.assertTrue("ERROR: Required build target 'core-image-minimal' has no buildable providers." in res.output, msg=res.output)
>
> def test_not_all_units_installed(self):
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2026-01-15 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 18:54 [PATCH v3 0/3] Overlayfs improvements uvv.mail
2026-01-14 18:54 ` [PATCH v3 1/3] overlayfs: Fix the QA skip for ignored mounts uvv.mail
2026-01-15 13:41 ` [OE-core] " Paul Barker
2026-01-15 21:18 ` Vyacheslav Yurkov
2026-01-14 18:54 ` [PATCH v3 2/3] oe-selftest: overlayfs: Make the test more deterministic uvv.mail
2026-01-15 13:53 ` Paul Barker [this message]
2026-01-14 18:54 ` [PATCH v3 3/3] oe-selftest: overlayfs: Add a demo case for /etc uvv.mail
2026-01-15 14:01 ` [OE-core] " Paul Barker
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=b06c5771c4f1405605db5aa21937a12d0ad73d2d.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=openembedded-core@lists.openembedded.org \
--cc=uvv.mail@gmail.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