From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] oeqa httpserver.py: fallback for multiprocessing import without bitbake
Date: Fri, 21 Nov 2025 15:39:39 +0200 [thread overview]
Message-ID: <aSBrm8wURTS-3e55@nuoska> (raw)
In-Reply-To: <4abba13482d2a5b933d34a0eb49edf693e0d7da3.camel@linuxfoundation.org>
Hi,
On Fri, Nov 21, 2025 at 01:34:44PM +0000, Richard Purdie wrote:
> On Fri, 2025-11-21 at 15:30 +0200, Mikko Rapeli wrote:
> > Hi,
> >
> > On Fri, Nov 21, 2025 at 01:27:56PM +0000, Richard Purdie wrote:
> > > On Fri, 2025-11-21 at 12:59 +0200, Mikko Rapeli via
> > > lists.openembedded.org wrote:
> > > > When testexport.bbclass is used, then build environment and
> > > > bitbake
> > > > may not be available when oeqa tests run.
> > > >
> > > > Fixes oeqa test execution:
> > > >
> > > > https://ledge.validation.linaro.org/scheduler/job/123974
> > > >
> > > > ImportError: Failed to import test module: apt
> > > > Traceback (most recent call last):
> > > > � File "/usr/lib/python3.13/unittest/loader.py", line 396, in
> > > > _find_test_path
> > > > ��� module = self._get_module_from_name(name)
> > > > � File "/usr/lib/python3.13/unittest/loader.py", line 339, in
> > > > _get_module_from_name
> > > > ��� __import__(name)
> > > > ��� ~~~~~~~~~~^^^^^^
> > > > � File "/lava-downloads/core-image-
> > > > sato/meta/lib/oeqa/runtime/cases/apt.py", line 8, in <module>
> > > > ��� from oeqa.utils.httpserver import HTTPService
> > > > � File "/lava-downloads/core-image-
> > > > sato/meta/lib/oeqa/utils/httpserver.py", line 9, in <module>
> > > > ��� from bb import multiprocessing
> > > > ModuleNotFoundError: No module named 'bb'
> > >
> > > Breaks with python 3.14.
> >
> > Understood but this would fix current test setups which still have
> > python 3.13.
>
> Where should we document that testexport only works if you have 3.13 or
> lower and not with 3.14? Who is going to maintain these requirements?
> This "not needing bb" requirement isn't really working well.
>
> I'd rather require lib/bb be present and included in the exported test
> data for example.
I agree this is the long term fix. If you don't want a "quick fix to unblock
testing" then I need to look into that. I was hoping to keep changes to
master branch minimal until release done.
Cheers,
-Mikko
prev parent reply other threads:[~2025-11-21 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 10:59 [PATCH] oeqa httpserver.py: fallback for multiprocessing import without bitbake Mikko Rapeli
2025-11-21 13:27 ` [OE-core] " Richard Purdie
2025-11-21 13:30 ` Mikko Rapeli
2025-11-21 13:34 ` Richard Purdie
2025-11-21 13:39 ` Mikko Rapeli [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=aSBrm8wURTS-3e55@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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