public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Paul Barker <paul@pbarker.dev>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2 2/4] overlayfs: oe-selftest: Make the test more deterministic
Date: Fri, 9 Jan 2026 09:49:25 +0100	[thread overview]
Message-ID: <52da37fd-54b6-4319-9c19-7ff8bb33dab8@gmail.com> (raw)
In-Reply-To: <1b37649b1cfa12e2c76f94f0589f8694e682e120.camel@pbarker.dev>

On 08.01.2026 14:33, Paul Barker wrote:
> On Wed, 2025-12-24 at 14:16 +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.
> The commit title says this is about determinism, but it's actually about
> supporting init systems other than systemd in the test case. I also
> think "selftest" should come before the component name, so perhaps it
> should be:
>
>    selftest: overlayfs: Support non-systemd init systems

The commit has nothing to do with non-systemd init systems, because the 
whole feature only works with systemd.

>
>> 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)
> The inverse logic here confused a few people on the patch review call.
> Could we add a comment at the same time, something like:
>
>    # If systemd is not enabled, we should see it listed as a missing
>    # distro feature
>
> That is just re-stating what the code does, but I think it's worthwhile
> here to avoid confusion.

This is already written a few lines above in the test description.

>
> Best regards,
>

Thanks,
Slava


  reply	other threads:[~2026-01-09  8:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-24 14:16 [PATCH v2 1/4] overlayfs: Fix QA failure uvv.mail
2025-12-24 14:16 ` [PATCH v2 2/4] overlayfs: oe-selftest: Make the test more deterministic uvv.mail
2026-01-08 13:33   ` [OE-core] " Paul Barker
2026-01-09  8:49     ` Vyacheslav Yurkov [this message]
     [not found]     ` <188903DB96F81C7D.2783356@lists.openembedded.org>
2026-01-14  7:45       ` Vyacheslav Yurkov
2025-12-24 14:16 ` [PATCH v2 3/4] overlayfs: Remove helper unit uvv.mail
2025-12-24 14:16 ` [PATCH v2 4/4] oe-selftest: overlayfs: Add a demo case for /etc uvv.mail
2026-01-08 13:46   ` [OE-core] " Paul Barker
2026-01-09  8:52     ` Vyacheslav Yurkov
2026-01-08 13:21 ` [OE-core] [PATCH v2 1/4] overlayfs: Fix QA failure Paul Barker
2026-01-13  9:32   ` [PATCH v3] overlayfs: Fix the QA skip for ignored mounts uvv.mail
2026-01-14 13:34     ` [OE-core] " Antonin Godard

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=52da37fd-54b6-4319-9c19-7ff8bb33dab8@gmail.com \
    --to=uvv.mail@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    /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