From: ChenQi <Qi.Chen@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH V2] runqemu: restore support to run without bitbake
Date: Wed, 4 Feb 2026 10:31:20 +0800 [thread overview]
Message-ID: <425e69ef-7bd6-458c-8c1c-45e6c5c1deb6@windriver.com> (raw)
In-Reply-To: <CANNYZj_obj+rntV-c1XEs=09-y=kVdqBxoD5M82euQ=5iT3MkA@mail.gmail.com>
On 2/3/26 18:10, Alexander Kanavin wrote:
> On Tue, 3 Feb 2026 at 03:21, Chen, Qi <Qi.Chen@windriver.com> wrote:
>> The steps for the test case should be simple and easy to reproduce.
>> Do you have any suggestion how to fix this issue?
>> Note that SDK does not have bitbake and OE metadata there.
>>
>> Or do you want me to first send out a patch to add an OEQA selftest case? Will that be accepted?
> I would suggest that you develop that patch first, and send it as a
> RFC (because it is expected to fail). I'd then be able to use the
> patch to reproduce the failure locally, and come up with suggestions
> (or maybe even patches) to address it. That would ensure the use case
> is officially supported, and will guard it against future regressions.
>
> Runqemu code is too complex and over-engineered, and to be honest,
> needs to be somehow simplified and rewritten, so when we see
> opportunities to simplify logic in it, we take it. Your use case fell
> victim of that because there were no tests or other indication that
> the code is necessary, but it wasn't intentional, and restoring
> support for the use case should be fine, but this time it should come
> with tests.
>
> Alex
Got it. I'll add the test case and send out the patch as RFC.
Regards,
Qi
prev parent reply other threads:[~2026-02-04 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 3:06 [OE-core][PATCH V2] runqemu: restore support to run without bitbake Qi.Chen
2026-02-02 15:52 ` Alexander Kanavin
2026-02-03 2:21 ` Chen, Qi
2026-02-03 10:10 ` Alexander Kanavin
2026-02-04 2:31 ` ChenQi [this message]
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=425e69ef-7bd6-458c-8c1c-45e6c5c1deb6@windriver.com \
--to=qi.chen@windriver.com \
--cc=alex.kanavin@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