[meta-filesystems][PATCH] overlayfs-tools: Inhibit tests on configure

[meta-filesystems][PATCH] overlayfs-tools: Inhibit tests on configure

[Marek Vasut]

In case the overlayfs-tools are built using meson, a test triggers
during meson setup phase during do_configure task. The test invokes
"sudo", which may not be present on the build machine. Skip the test
at meson setup phase. Tests should be executed separately on demand
using "meson test" command instead, and invoking "sudo" and expecting
it to work during do_configure is unusual.

"
ERROR: overlayfs-tools-v2025.01-r0 do_configure: meson setup failed
...
| Run-time dependency musl-fts found: NO (tried pkgconfig)
| Library m found: YES
| Program test_cases/run_tests.py found: YES (/home/oe/build-some-target/tmp/work/arm64-distro-linux/overlayfs-tools/v2025.01/sources/overlayfs-tools-v2025.01/test_cases/run_tests.py)
|
| ../sources/overlayfs-tools-v2025.01/meson.build:94:0: ERROR: Program 'sudo' not found or not executable
|
| A full log can be found at /home/oe/build-some-target/tmp/work/arm64-distro-linux/overlayfs-tools/v2025.01/build/meson-logs/meson-log.txt
|
| Last 10 lines of meson-log.txt:
| Code:
| int main(void) { return 0; }
"

Signed-off-by: Marek Vasut <marek.vasut@mailbox.org>
---
Cc: Alexander Kanavin <alex@linutronix.de>
Cc: Ankur Tyagi <ankur.tyagi85@gmail.com>
Cc: Khem Raj <khem.raj@oss.qualcomm.com>
Cc: Vyacheslav Yurkov <uvv.mail@gmail.com>
---
 .../recipes-utils/overlayfs/overlayfs-tools_2025.01.bb        | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/meta-filesystems/recipes-utils/overlayfs/overlayfs-tools_2025.01.bb b/meta-filesystems/recipes-utils/overlayfs/overlayfs-tools_2025.01.bb
index 8583a0e2cb..3b5963bb26 100644
--- a/meta-filesystems/recipes-utils/overlayfs/overlayfs-tools_2025.01.bb
+++ b/meta-filesystems/recipes-utils/overlayfs/overlayfs-tools_2025.01.bb
@@ -14,3 +14,7 @@ UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>\d+(\.\d+)+)"
 inherit meson pkgconfig
 
 DEPENDS:append:libc-musl = " fts"
+
+do_configure:prepend() {
+	sed -i '/Custom targets for testing overlay function/,/command : .*permanent...changes/ d' ${S}/meson.build
+}
-- 
2.53.0

Re: [meta-filesystems][PATCH] overlayfs-tools: Inhibit tests on configure

[Vyacheslav Yurkov]

Thanks for the patch Marek.

Could you please explain how you hit the issue? I can't reproduce it.
The sudo is required only for tests, which is a custom meson target. 
It's not supposed to be called during configure.

Slava

On 21.10.2026 15:53, Marek Vasut wrote:
> In case the overlayfs-tools are built using meson, a test triggers
> during meson setup phase during do_configure task. The test invokes
> "sudo", which may not be present on the build machine. Skip the test
> at meson setup phase. Tests should be executed separately on demand
> using "meson test" command instead, and invoking "sudo" and expecting
> it to work during do_configure is unusual.
>
> "
> ERROR: overlayfs-tools-v2025.01-r0 do_configure: meson setup failed
> ...
> | Run-time dependency musl-fts found: NO (tried pkgconfig)
> | Library m found: YES
> | Program test_cases/run_tests.py found: YES (/home/oe/build-some-target/tmp/work/arm64-distro-linux/overlayfs-tools/v2025.01/sources/overlayfs-tools-v2025.01/test_cases/run_tests.py)
> |
> | ../sources/overlayfs-tools-v2025.01/meson.build:94:0: ERROR: Program 'sudo' not found or not executable
> |
> | A full log can be found at /home/oe/build-some-target/tmp/work/arm64-distro-linux/overlayfs-tools/v2025.01/build/meson-logs/meson-log.txt
> |
> | Last 10 lines of meson-log.txt:
> | Code:
> | int main(void) { return 0; }
> "
>
> Signed-off-by: Marek Vasut <marek.vasut@mailbox.org>
> ---
> Cc: Alexander Kanavin <alex@linutronix.de>
> Cc: Ankur Tyagi <ankur.tyagi85@gmail.com>
> Cc: Khem Raj <khem.raj@oss.qualcomm.com>
> Cc: Vyacheslav Yurkov <uvv.mail@gmail.com>
> ---
>   .../recipes-utils/overlayfs/overlayfs-tools_2025.01.bb        | 4 ++++
>   1 file changed, 4 insertions(+)
>
> diff --git a/meta-filesystems/recipes-utils/overlayfs/overlayfs-tools_2025.01.bb b/meta-filesystems/recipes-utils/overlayfs/overlayfs-tools_2025.01.bb
> index 8583a0e2cb..3b5963bb26 100644
> --- a/meta-filesystems/recipes-utils/overlayfs/overlayfs-tools_2025.01.bb
> +++ b/meta-filesystems/recipes-utils/overlayfs/overlayfs-tools_2025.01.bb
> @@ -14,3 +14,7 @@ UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>\d+(\.\d+)+)"
>   inherit meson pkgconfig
>   
>   DEPENDS:append:libc-musl = " fts"
> +
> +do_configure:prepend() {
> +	sed -i '/Custom targets for testing overlay function/,/command : .*permanent...changes/ d' ${S}/meson.build
> +}

Re: [meta-filesystems][PATCH] overlayfs-tools: Inhibit tests on configure

[Marek Vasut]

On 10/21/26 5:09 PM, Vyacheslav Yurkov wrote:
> Thanks for the patch Marek.
> 
> Could you please explain how you hit the issue? I can't reproduce it.
> The sudo is required only for tests, which is a custom meson target. 
> It's not supposed to be called during configure.
$ bitbake -c configure overlayfs-tools

on aarch64 (STM32MP25) target (not using the ST layers).

I would also expect the tests to NOT run during configure.

It also happens in OE wrynose builds, but not in OE scarthgap builds.

Re: [meta-filesystems][PATCH] overlayfs-tools: Inhibit tests on configure

[Vyacheslav Yurkov]

On 21.10.2026 18:27, Marek Vasut wrote:
> On 10/21/26 5:09 PM, Vyacheslav Yurkov wrote:
>> Thanks for the patch Marek.
>>
>> Could you please explain how you hit the issue? I can't reproduce it.
>> The sudo is required only for tests, which is a custom meson target. 
>> It's not supposed to be called during configure.
> $ bitbake -c configure overlayfs-tools
>
> on aarch64 (STM32MP25) target (not using the ST layers).
>
> I would also expect the tests to NOT run during configure.
>
> It also happens in OE wrynose builds, but not in OE scarthgap builds.

I was not able to reproduce it either on wrynose or on master. Although 
I usually build x86_64 / arm32, but I don't think that makes a difference.

Any chance your BSP adds a "meson test" call at any point?

Re: [meta-filesystems][PATCH] overlayfs-tools: Inhibit tests on configure

[Marek Vasut]

On 10/22/26 2:24 PM, Vyacheslav Yurkov wrote:
> On 21.10.2026 18:27, Marek Vasut wrote:
>> On 10/21/26 5:09 PM, Vyacheslav Yurkov wrote:
>>> Thanks for the patch Marek.
>>>
>>> Could you please explain how you hit the issue? I can't reproduce it.
>>> The sudo is required only for tests, which is a custom meson target. 
>>> It's not supposed to be called during configure.
>> $ bitbake -c configure overlayfs-tools
>>
>> on aarch64 (STM32MP25) target (not using the ST layers).
>>
>> I would also expect the tests to NOT run during configure.
>>
>> It also happens in OE wrynose builds, but not in OE scarthgap builds.
> 
> I was not able to reproduce it either on wrynose or on master. Although 
> I usually build x86_64 / arm32, but I don't think that makes a difference.
> 
> Any chance your BSP adds a "meson test" call at any point?

Can you try this:

"
# conf/local.conf
MACHINE ??= "qemux86-64"
USER_CLASSES ?= "buildstats"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS ??= "\
     STOPTASKS,${TMPDIR},1G,100K \
     STOPTASKS,${DL_DIR},1G,100K \
     STOPTASKS,${SSTATE_DIR},1G,100K \
     STOPTASKS,/tmp,100M,100K \
     HALT,${TMPDIR},100M,1K \
     HALT,${DL_DIR},100M,1K \
     HALT,${SSTATE_DIR},100M,1K \
     HALT,/tmp,10M,1K"

CONF_VERSION = "2"
"

"
# conf/bblayers.conf
LCONF_VERSION = "7"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
   /oe-core___wrynose-6.0/meta \
   /meta-openembedded___wrynose-6.0/meta-oe/ \
   /meta-openembedded___wrynose-6.0/meta-python/ \
   /meta-openembedded___wrynose-6.0/meta-networking/ \
   /meta-openembedded___wrynose-6.0/meta-filesystems/ \
   "
"

$ . oe-init-build-env /path/to/builddir
$ MACHINE="qemux86-64" DISTRO="nodistro" bitbake -c configure 
overlayfs-tools

?

Also, please run 'which sudo' and check whether sudo isn't actually 
installed on your build machine (it is NOT installed on mine, because it 
is a minimal container)

Re: [meta-filesystems][PATCH] overlayfs-tools: Inhibit tests on configure

[Vyacheslav Yurkov]

On 22.10.2026 17:13, Marek Vasut wrote:
> Can you try this:
>
> "
> # conf/local.conf
> MACHINE ??= "qemux86-64"
> USER_CLASSES ?= "buildstats"
> PATCHRESOLVE = "noop"
> BB_DISKMON_DIRS ??= "\
>     STOPTASKS,${TMPDIR},1G,100K \
>     STOPTASKS,${DL_DIR},1G,100K \
>     STOPTASKS,${SSTATE_DIR},1G,100K \
>     STOPTASKS,/tmp,100M,100K \
>     HALT,${TMPDIR},100M,1K \
>     HALT,${DL_DIR},100M,1K \
>     HALT,${SSTATE_DIR},100M,1K \
>     HALT,/tmp,10M,1K"
>
> CONF_VERSION = "2"
> "
>
> "
> # conf/bblayers.conf
> LCONF_VERSION = "7"
> BBPATH = "${TOPDIR}"
> BBFILES ?= ""
> BBLAYERS ?= " \
>   /oe-core___wrynose-6.0/meta \
>   /meta-openembedded___wrynose-6.0/meta-oe/ \
>   /meta-openembedded___wrynose-6.0/meta-python/ \
>   /meta-openembedded___wrynose-6.0/meta-networking/ \
>   /meta-openembedded___wrynose-6.0/meta-filesystems/ \
>   "
> "
>
> $ . oe-init-build-env /path/to/builddir
> $ MACHINE="qemux86-64" DISTRO="nodistro" bitbake -c configure 
> overlayfs-tools
>
> ?
>
> Also, please run 'which sudo' and check whether sudo isn't actually 
> installed on your build machine (it is NOT installed on mine, because 
> it is a minimal container)

Thanks, I guess the container without a `sudo` is the reason (somehow I 
always had it in mines).

If you are OK with this fix 
https://github.com/kmxz/overlayfs-tools/pull/34 , we can bump a revision 
after that.

Slava

Re: [oe] [meta-filesystems][PATCH] overlayfs-tools: Inhibit tests on configure

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]

On Thu, Oct 22, 2026 at 11:24 PM Vyacheslav Yurkov via
lists.openembedded.org <uvv.mail=gmail.com@lists.openembedded.org> wrote:

> On 22.10.2026 17:13, Marek Vasut wrote:
> > Can you try this:
> >
> > "
> > # conf/local.conf
> > MACHINE ??= "qemux86-64"
> > USER_CLASSES ?= "buildstats"
> > PATCHRESOLVE = "noop"
> > BB_DISKMON_DIRS ??= "\
> >     STOPTASKS,${TMPDIR},1G,100K \
> >     STOPTASKS,${DL_DIR},1G,100K \
> >     STOPTASKS,${SSTATE_DIR},1G,100K \
> >     STOPTASKS,/tmp,100M,100K \
> >     HALT,${TMPDIR},100M,1K \
> >     HALT,${DL_DIR},100M,1K \
> >     HALT,${SSTATE_DIR},100M,1K \
> >     HALT,/tmp,10M,1K"
> >
> > CONF_VERSION = "2"
> > "
> >
> > "
> > # conf/bblayers.conf
> > LCONF_VERSION = "7"
> > BBPATH = "${TOPDIR}"
> > BBFILES ?= ""
> > BBLAYERS ?= " \
> >   /oe-core___wrynose-6.0/meta \
> >   /meta-openembedded___wrynose-6.0/meta-oe/ \
> >   /meta-openembedded___wrynose-6.0/meta-python/ \
> >   /meta-openembedded___wrynose-6.0/meta-networking/ \
> >   /meta-openembedded___wrynose-6.0/meta-filesystems/ \
> >   "
> > "
> >
> > $ . oe-init-build-env /path/to/builddir
> > $ MACHINE="qemux86-64" DISTRO="nodistro" bitbake -c configure
> > overlayfs-tools
> >
> > ?
> >
> > Also, please run 'which sudo' and check whether sudo isn't actually
> > installed on your build machine (it is NOT installed on mine, because
> > it is a minimal container)
>
> Thanks, I guess the container without a `sudo` is the reason (somehow I
> always had it in mines).
>
> If you are OK with this fix
> https://github.com/kmxz/overlayfs-tools/pull/34 , we can bump a revision
> after that.
>

This means no ptests ?


>
> Slava
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#131324):
> https://lists.openembedded.org/g/openembedded-devel/message/131324
> Mute This Topic: https://lists.openembedded.org/mt/121866846/1997914
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [
> raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 3681 bytes --]

Re: [oe] [meta-filesystems][PATCH] overlayfs-tools: Inhibit tests on configure

[Marek Vasut]

On 10/23/26 9:07 AM, Vyacheslav Yurkov wrote:

Hello everyone,

>>     Thanks, I guess the container without a `sudo` is the reason
>>     (somehow I
>>     always had it in mines).
>>
>>     If you are OK with this fix
>>     https://github.com/kmxz/overlayfs-tools/pull/34 , we can bump a
>>     revision
>>     after that.

For meta-filesystems/master , bumping the version is fine.
For meta-filesystems/wrynose , a patch would have to be added.
This is fine.

>> This means no ptests ?
>>
> Can be added in the recipe via PACKAGECONFIG

Is it possible to test the overlayfs-tools without invoking sudo ? 
(reading the documentation and the rationale for sudo, I guess not in 
any performant easy way)