From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org,
Ricardo Martincoski <ricardo.martincoski@datacom.com.br>,
Jimmy Durand Wesolowski <jimmy.wesolowski@mobileye.com>,
Julien Olivain <ju.o@free.fr>,
guenther.harrasser@mobileye.com
Subject: Re: [Buildroot] [PATCH v2 1/1] support/testing: transfer config in environment instead of class variables
Date: Sat, 30 May 2026 16:32:02 +0200 [thread overview]
Message-ID: <ahr0yTuMUlfUWvvn@windsurf> (raw)
In-Reply-To: <20260306215539.510232-1-fiona.klute@gmx.de>
On Fri, Mar 06, 2026 at 10:55:39PM +0100, Fiona Klute via buildroot wrote:
> Passing runtime configuration to tests in BRConfigTest class variables
> requires the "fork" start method for multiprocessing. With
> "forkserver" (default for POSIX platforms since Python 3.14) class
> variables modified in the parent process are lost, because the child
> process does not inherit the full Python state. This broke the way
> support/testing/run-tests sets configuration for BRConfigTest, so a
> start method override was added in commit
> 3d2141bceefda32bef06ddda594eaf8665913276.
>
> Instead this patch adds a settings dataclass (requires Python >= 3.7)
> which is serialized into an environment variable from run-tests and
> read during BRConfigTest.__init__(). Reading is skipped if the
> environment variable is not set so test discovery (not execution)
> works without configuration (e.g. utils/get-developers uses this).
>
> With that, run-tests no longer relies on a specific multiprocessing
> start method.
>
> Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
Thanks a lot for having cleaned up my terrible code! Applied to next.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-05-30 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 21:55 [Buildroot] [PATCH v2 1/1] support/testing: transfer config in environment instead of class variables Fiona Klute via buildroot
2026-05-30 14:32 ` Thomas Petazzoni via buildroot [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=ahr0yTuMUlfUWvvn@windsurf \
--to=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 \
--cc=thomas.petazzoni@bootlin.com \
/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