From: uvv.mail@gmail.com
To: openembedded-core@lists.openembedded.org
Cc: Vyacheslav Yurkov <uvv.mail@gmail.com>
Subject: [PATCH 1/4] overlayfs: Fix QA failure
Date: Mon, 22 Dec 2025 11:38:37 +0000 [thread overview]
Message-ID: <20251222113840.2163929-1-uvv.mail@gmail.com> (raw)
From: Vyacheslav Yurkov <uvv.mail@gmail.com>
The QA check for skipped mounts happens twice, at parsing stage and at
rootfs postprocessing. Fix the former, because it didn't happen properly.
Signed-off-by: Vyacheslav Yurkov <uvv.mail@gmail.com>
---
meta/lib/oe/overlayfs.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oe/overlayfs.py b/meta/lib/oe/overlayfs.py
index 8b88900f71..dbfed317c0 100644
--- a/meta/lib/oe/overlayfs.py
+++ b/meta/lib/oe/overlayfs.py
@@ -36,7 +36,8 @@ def unitFileList(d):
# check that we have required mount points set first
requiredMountPoints = d.getVarFlags('OVERLAYFS_WRITABLE_PATHS')
for mountPoint in requiredMountPoints:
- if mountPoint not in overlayMountPoints:
+ qaSkip = (d.getVarFlag("OVERLAYFS_QA_SKIP", mountPoint) or "").split()
+ if mountPoint not in overlayMountPoints and not "mount-configured" in qaSkip:
bb.fatal("Missing required mount point for OVERLAYFS_MOUNT_POINT[%s] in your MACHINE configuration" % mountPoint)
for mountPoint in overlayMountPoints:
next reply other threads:[~2025-12-22 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 11:38 uvv.mail [this message]
2025-12-22 11:38 ` [PATCH 2/4] overlayfs: oe-selftest: Make the test more deterministic uvv.mail
2025-12-22 11:38 ` [PATCH 3/4] overlayfs: Remove helper unit uvv.mail
2025-12-22 11:38 ` [PATCH 4/4] oe-selftest: overlayfs: Add a demo case for /etc uvv.mail
2025-12-24 12:07 ` [OE-core] " Mathieu Dubois-Briand
2025-12-24 14:12 ` Vyacheslav Yurkov
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=20251222113840.2163929-1-uvv.mail@gmail.com \
--to=uvv.mail@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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