From: Peter Korsgaard <peter@korsgaard.com>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org,
Ricardo Martincoski <ricardo.martincoski@datacom.com.br>,
Julien Olivain <ju.o@free.fr>,
Jimmy Durand Wesolowski <jimmy.wesolowski@mobileye.com>,
guenther.harrasser@mobileye.com
Subject: Re: [Buildroot] [PATCH 1/1] support/testing: transfer config in environment instead of class variables
Date: Sat, 28 Feb 2026 23:21:07 +0100 [thread overview]
Message-ID: <87wlzwo6gc.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <4de55993-a547-418b-83a5-b5e5549480fd@gmx.de> (Fiona Klute's message of "Sat, 28 Feb 2026 21:41:04 +0100")
>>>>> "Fiona" == Fiona Klute <fiona.klute@gmx.de> writes:
Hi,
>> Wouldn't that work?
> No, because with the execution order in support/testing/run-tests that
> is the *first* call (so it would still happen, except on pre-3.14
> Python where "fork" is the default), the second one (which then causes
> an exception) happens in the Debian-patched "mp" plugin of Nose,
> specifically when it's loaded. Otherwise we could just catch the
> exception and ignore it if the start method is what we expect.
Ahh, true.
> The main issue is with Debian, of course (without that incorrect patch
> run-tests would work as it is), but relying on a specific
> multiprocessing start method was always fragile. For stable branches I
> think it'd be fair to point at the problem being a Debian bug, if this
> patch (or something similar) is considered too big to backport. The
> buggy Nose version is only in unstable & testing right now, I hope
> there'll be a properly fixed one before the Forky release.
What we could also do is to only add the workaround for python >= 3.14.x
(which is not yet in Debian), E.G.
if sys.version_info >= (3,14):
multiprocessing.set_start_method('fork')
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-28 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 19:21 [Buildroot] [PATCH 1/1] support/testing: transfer config in environment instead of class variables Fiona Klute via buildroot
2026-02-28 19:50 ` Peter Korsgaard
2026-02-28 20:41 ` Fiona Klute via buildroot
2026-02-28 22:21 ` Peter Korsgaard [this message]
2026-02-28 22:30 ` Fiona Klute via buildroot
2026-03-01 10:10 ` Peter Korsgaard
2026-03-01 10:11 ` Peter Korsgaard
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=87wlzwo6gc.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=guenther.harrasser@mobileye.com \
--cc=jimmy.wesolowski@mobileye.com \
--cc=ju.o@free.fr \
--cc=ricardo.martincoski@datacom.com.br \
/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