From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 3/3] ci: build: shuffle goal and prerequisite ordering
Date: Mon, 1 Sep 2025 17:38:05 +0200 [thread overview]
Message-ID: <20250901153852.2554758-4-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20250901153852.2554758-1-a.fatoum@pengutronix.de>
Now that the container has been newly updated to Debian Trixie, we have
GNU make v4.4.1 available. v4.4 introduced a new --shuffle option
that shuffles goal and prerequisite ordering to hopefully catch issues
around non-deterministic build order in parallel makefiles.
Let's enable this option for all our defconfig builds. When a build
fails, make will also print to stderr a shuffle=<integer> line.
The integer can be passed to --shuffle locally when trying to reproduce
the breakage.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
.github/workflows/build-defconfigs.yml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/.github/workflows/build-defconfigs.yml b/.github/workflows/build-defconfigs.yml
index c95c56b6ba88..e99dfe595bf0 100644
--- a/.github/workflows/build-defconfigs.yml
+++ b/.github/workflows/build-defconfigs.yml
@@ -39,6 +39,8 @@ jobs:
./test/generate-dummy-fw.sh
+ export GNUMAKEFLAGS=--shuffle
+
./MAKEALL -O build-${{matrix.arch}} -l "" -v 0 \
-k common/boards/configs/disable_size_check.config \
-k common/boards/configs/disable_target_tools.config \
--
2.47.2
prev parent reply other threads:[~2025-09-01 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 15:38 [PATCH 0/3] ci: update to Trixie to use make --shuffle Ahmad Fatoum
2025-09-01 15:38 ` [PATCH 1/3] ci: container: update components installed on top to newest versions Ahmad Fatoum
2025-09-01 15:38 ` [PATCH 2/3] ci: container: update to Debian Trixie Ahmad Fatoum
2025-09-01 15:38 ` Ahmad Fatoum [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=20250901153852.2554758-4-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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