From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Antonin Godard <antonin.godard@bootlin.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/3] oeqa/selftest/bblock/fitimage/sstatetests: Fix changing MACHINE during the test
Date: Fri, 10 Oct 2025 16:40:58 +0100 [thread overview]
Message-ID: <c62656752249cec0bdcf7699ff69f7471a118029.camel@linuxfoundation.org> (raw)
In-Reply-To: <DDER4TNFACYK.197FU3Y7W8OXL@bootlin.com>
On Fri, 2025-10-10 at 17:36 +0200, Antonin Godard wrote:
> On Mon Oct 6, 2025 at 3:14 PM CEST, Richard Purdie via
> lists.openembedded.org wrote:
> > With config fragments, changing MACHINE in the test like this no
> > longer works. Use the forcevarable override to allow it to work.
> > This also needs a tweak to bitbake to work correctly, sent
> > seperately. Whilst ugly, this avoids the need to start changing
> > config fragments within oeqa right now.
>
> Why not move the inclusion of auto.conf after the addfragments call
> in bitbake.conf? Maybe this triggers another issue, but I'm just
> wondering.
It would change behaviour, there is a lot of things out there which
assume the current ordering and we don't really want to change it as
the breakage is potentially very subtle and not obvious.
Cheers,
Richard
next prev parent reply other threads:[~2025-10-10 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 13:14 [PATCH 1/3] oeqa/selftest/bblock/fitimage/sstatetests: Fix changing MACHINE during the test Richard Purdie
2025-10-06 13:14 ` [PATCH 2/3] oeqa/selftest/oescripts: Ensure buildstats is present Richard Purdie
2025-10-06 13:14 ` [PATCH 3/3] oeqa/selftest/buildhistory: Fix test if USER_CLASSES is unset Richard Purdie
2025-10-10 15:36 ` [OE-core] [PATCH 1/3] oeqa/selftest/bblock/fitimage/sstatetests: Fix changing MACHINE during the test Antonin Godard
2025-10-10 15:40 ` Richard Purdie [this message]
2025-10-10 15:42 ` 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=c62656752249cec0bdcf7699ff69f7471a118029.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=antonin.godard@bootlin.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