From: Alyssa Ross <hi@alyssa.is>
To: Santiago Vila <sanvila@debian.org>, util-linux@vger.kernel.org
Cc: Karel Zak <kzak@redhat.com>
Subject: Re: Parallel build failures with util-linux 2.40
Date: Sun, 19 May 2024 10:13:39 +0200 [thread overview]
Message-ID: <87cypigqx8.fsf@alyssa.is> (raw)
In-Reply-To: <3dfa7d03-f2bf-4d6f-8387-98ec999243bf@debian.org>
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
Santiago Vila <sanvila@debian.org> writes:
> Hello.
>
> In some cases, make --shuffle option (available in GNU make 4.4)
> "amplifies" the probability that a Makefile bug shows up.
> I suggest that you people give it a try.
>
> There is a blog entry from the author explaining --shuffle option:
>
> https://trofi.github.io/posts/238-new-make-shuffle-mode.html
>
> [ I'm just a long-time lurker in this list, but maybe this could help ]
Thanks for the suggestion, but I tried running with --shuffle for hours
before submitting my report, but wasn't able to reproduce that way. :(
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2024-05-19 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 10:01 Parallel build failures with util-linux 2.40 Alyssa Ross
2024-05-15 14:22 ` Karel Zak
2024-05-15 16:18 ` Alyssa Ross
2024-05-18 19:54 ` Alyssa Ross
2024-05-18 20:15 ` Santiago Vila
2024-05-19 8:13 ` Alyssa Ross [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=87cypigqx8.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=kzak@redhat.com \
--cc=sanvila@debian.org \
--cc=util-linux@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).