From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: GNU Guix (pull?) on i686 broke after zstd grafting
Date: Wed, 10 Mar 2021 11:43:28 +0100 [thread overview]
Message-ID: <e6accd79151aa5ae94fddfa8215dd27480dc7386.camel@zaclys.net> (raw)
In-Reply-To: <874khj5m6h.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On Wed, 2021-03-10 at 11:37 +0100, Ludovic Courtès wrote:
> Hi Léo,
Hi Ludo!
> So I think there’s a genuine bug here. Could you take a look? At
> worst, we should skip the offending test on i686 (and perhaps
> ARMv7?).
I reported upstream and I got an answer, waiting for fix but also we
could do something based on their comment:
> So now that we have plausible explanation, what can be done about it
> ?
>
> - Ignore this test. It's a just test error. Disable it.
> - Change the test, so that it passes. For example, use a fixed nb of
> threads, like -T4.
> - Update the rule regulating -T0, determining automatically a nb of
> threads based on present nb of cores. Make it conditional for 32-bit
> systems, select a limit for this case (slightly more complex, will
> take time).
> - Update the thread-pool policy to allocate new threads only when
> needed, instead of up front (definitely more complex, will take even
> more time).
I am very tired now however, also not sure how to disable individual
tests there.
Léo
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-10 10:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 5:09 GNU Guix (pull?) on i686 broke after zstd grafting Léo Le Bouter
2021-03-06 5:30 ` Léo Le Bouter
2021-03-10 10:37 ` Ludovic Courtès
2021-03-10 10:43 ` Léo Le Bouter [this message]
2021-03-11 2:11 ` Léo Le Bouter
2021-03-11 9:37 ` zimoun
2021-03-11 9:40 ` Léo Le Bouter
2021-03-11 9:58 ` zimoun
2021-03-11 10:05 ` Léo Le Bouter
2021-03-16 16:34 ` Release 1.2.1: zstd 1.4.4 -> 1.4.9: grafting or core-updates? zimoun
2021-03-16 17:06 ` Léo Le Bouter
2021-03-16 17:48 ` Leo Famulari
2021-03-16 18:03 ` Léo Le Bouter
2021-03-16 17:59 ` zimoun
2021-03-16 17:55 ` Leo Famulari
2021-03-16 18:08 ` Léo Le Bouter
2021-03-16 18:46 ` zimoun
2021-03-16 18:50 ` Léo Le Bouter
2021-03-16 19:04 ` zimoun
2021-03-16 18:19 ` zimoun
2021-03-16 18:26 ` Léo Le Bouter
2021-03-16 19:18 ` Leo Famulari
2021-03-16 19:25 ` zimoun
2021-03-16 19:29 ` Leo Famulari
2021-03-16 21:46 ` Security-czar needed? WAS: " Bengt Richter
2021-03-16 22:03 ` Leo Famulari
2021-03-17 6:24 ` Léo Le Bouter
2021-03-17 14:00 ` zimoun
2021-03-16 21:47 ` Maxime Devos
2021-03-16 20:53 ` Tobias Geerinckx-Rice
2021-03-16 21:18 ` Vincent Legoll
2021-03-16 21:56 ` Leo Famulari
2021-03-17 6:40 ` Léo Le Bouter
2021-03-30 0:35 ` Léo Le Bouter
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e6accd79151aa5ae94fddfa8215dd27480dc7386.camel@zaclys.net \
--to=lle-bout@zaclys.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).