mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: sha@pengutronix.de, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH] MAKEALL: print --shuffle seed used for initial make *_defconfig
Date: Tue, 21 Oct 2025 09:57:42 +0200	[thread overview]
Message-ID: <20251021075742.4016898-1-a.fatoum@pengutronix.de> (raw)

We run make *_defconfig once initially, so that we can get a .config to
grep for CONFIG_ARM64 inside. The grepping occasionally[1] fails in CI:

  grep: build-arm-multi_v8_defconfig/.config: No such file or directory

This might be because of the shuffling of the dependencies, but because
make itself doesn't fail, we don't get the shuffle seed in the log.

Let's collect it and print it to help track down this issue.

[1]: https://github.com/barebox/barebox/actions/runs/18654962634/job/53181695019

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 MAKEALL | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/MAKEALL b/MAKEALL
index d47f0204f1f1..b953da9cccdd 100755
--- a/MAKEALL
+++ b/MAKEALL
@@ -135,7 +135,11 @@ do_build_defconfig() {
 	[ -n "$logdir" ] && mkdir -p "${logdir}/${defconfig}"
 
 	MAKE="make -j${JOBS} ARCH=${arch} O=${BUILDDIR}"
-	${MAKE} ${defconfig} &>/dev/null
+	shuffle=$(${MAKE} --debug=basic ${defconfig} 2>&1 | sed -n 's/.*Enabled shuffle mode: //p;T;q')
+
+	if [ -n "$shuffle" ]; then
+		report "Probing ${arch} ${defconfig} (--shuffle=$shuffle)\n" >&2
+	fi
 
 	if [ ${arch} = "arm" ]; then
 		grep -q "CONFIG_ARM64=y" ${BUILDDIR}/.config
-- 
2.47.3




             reply	other threads:[~2025-10-21  7:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21  7:57 Ahmad Fatoum [this message]
2025-10-22  9:25 ` Sascha Hauer

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=20251021075742.4016898-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=sha@pengutronix.de \
    /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