From: Trevor Woerner <twoerner@gmail.com>
To: mikko.rapeli@linaro.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] oeqa wic.py: clean image build dir before rebuild in test_permissions()
Date: Mon, 14 Apr 2025 16:56:14 -0400 [thread overview]
Message-ID: <20250414205613.GA8398@localhost> (raw)
In-Reply-To: <20250407110946.47038-1-mikko.rapeli@linaro.org>
On Mon 2025-04-07 @ 02:09:45 PM, Mikko Rapeli via lists.openembedded.org wrote:
> The test builds images using wic and then with bitbake
> and compares results. This fails at least on aarch64
> build machine and multiple target machines due to
> pseudo errors. Fix by cleaning the build recipe
> build directory before rebuild.
>
> Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
> ---
> meta/lib/oeqa/selftest/cases/wic.py | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/lib/oeqa/selftest/cases/wic.py b/meta/lib/oeqa/selftest/cases/wic.py
> index 4f5d43b5ee..55c655cd6d 100644
> --- a/meta/lib/oeqa/selftest/cases/wic.py
> +++ b/meta/lib/oeqa/selftest/cases/wic.py
> @@ -674,6 +674,7 @@ part /etc --source rootfs --fstype=ext4 --change-directory=etc
>
> config = 'IMAGE_FSTYPES += "wic"\nWKS_FILE = "%s"\n' % wks_file
> self.append_config(config)
> + bitbake('-c clean core-image-minimal')
> bitbake('core-image-minimal')
> tmpdir = os.path.join(get_bb_var('WORKDIR', 'core-image-minimal'),'build-wic')
>
I have seen this issue too, but it is intermittent for me; is this an
intermittent issue with you as well? This feels a lot more like a hack rather
than a solution.
next prev parent reply other threads:[~2025-04-14 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 11:09 [PATCH] oeqa wic.py: clean image build dir before rebuild in test_permissions() Mikko Rapeli
2025-04-14 20:56 ` Trevor Woerner [this message]
2025-04-15 5:07 ` [OE-core] " Mikko Rapeli
2025-04-24 10:38 ` Richard Purdie
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=20250414205613.GA8398@localhost \
--to=twoerner@gmail.com \
--cc=mikko.rapeli@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.