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: Sun, 01 Mar 2026 11:11:14 +0100 [thread overview]
Message-ID: <87ldgboo59.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87pl5noo6y.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Sun, 01 Mar 2026 11:10:13 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
Hi,
> Another hacky workaround would be to monkey patch set_start_method() to
> ignore the call from nose2, E.G.:
> if multiprocessing.get_start_method() != 'fork':
> multiprocessing.set_start_method('fork')
> multiprocessing.set_start_method = = lambda *args: None
Ehh, without the 2nd '=' naturally ;)
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-03-01 10:11 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
2026-02-28 22:30 ` Fiona Klute via buildroot
2026-03-01 10:10 ` Peter Korsgaard
2026-03-01 10:11 ` Peter Korsgaard [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=87ldgboo59.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