From: Andy Wingo <wingo@igalia.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org, 27476@debbugs.gnu.org
Subject: bug#27476: guix pull fails on powerful server
Date: Mon, 25 Sep 2017 09:27:45 +0200 [thread overview]
Message-ID: <87k20nz18u.fsf@igalia.com> (raw)
In-Reply-To: <87377esu1a.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 22 Sep 2017 16:10:57 +0200")
On Fri 22 Sep 2017 16:10, ludo@gnu.org (Ludovic Courtès) writes:
> Hi Ricardo,
>
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> The following derivation will be built:
>> /gnu/store/yvyfkns3w3vm7ynwbr7mvxcmin4gd2a0-guix-latest.drv
>> copying and compiling to '/gnu/store/7m52dkr98nhwgpsx20mmpwyw2yzj58d3-guix-latest' with Guile 2.2.2...
>> loading... 25.4% of 629 filesrandom seed for tests: 1506066913
>> loading... 99.8% of 629 files
>> compiling... 69.2% of 629 filesice-9/threads.scm:289:22: In procedure loop:
>> ice-9/threads.scm:289:22: Syntax error:
>> guix/scripts.scm:130:2: >>=: >>= (bind) used outside of 'with-monad' in form (>>= (apply set-build-options* #:use-substitutes
>> ptions)) (lambda (unused-value) (mbegin %store-monad (mlet %store-monad ((derivation (origin->derivation (package-source pack
>> tutes? use-substitutes? #:dry-run? dry-run?) (return (show-derivation-outputs derivation)))))))
>
> This was reported at <https://bugs.gnu.org/27476>, and I suspect a
> thread-safety issue. However, syntax parameters are purely functional
> AFAICS, so I fail to see why multithreading could be a problem.
>
> Andy, any idea what could be causing this?
I have heard of but not seen a number of similar bugs: errors that
"can't happen" but which appear under multiple threads. I don't know
what underlying pattern is. Has anyone found a test case that reliably
reproduces?
Andy
next prev parent reply other threads:[~2017-09-25 7:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 8:38 guix pull fails on powerful server Ricardo Wurmus
2017-09-22 14:10 ` bug#27476: " Ludovic Courtès
2017-09-25 7:27 ` Andy Wingo [this message]
2017-09-25 13:03 ` Ludovic Courtès
2017-09-25 14:02 ` bug#27476: " Ricardo Wurmus
2017-09-30 7:59 ` Ricardo Wurmus
2017-10-03 20:29 ` Marius Bakke
2017-10-04 13:15 ` Ricardo Wurmus
2017-10-04 15:09 ` Clément Lassieur
2017-10-04 16:17 ` bug#27476: " Ricardo Wurmus
2017-10-07 15:11 ` Ludovic Courtès
2017-10-10 7:17 ` Ricardo Wurmus
2017-10-10 11:32 ` Ludovic Courtès
2017-10-12 13:37 ` bug#27476: " Ludovic Courtès
2017-10-13 20:29 ` Ricardo Wurmus
2017-10-13 21:04 ` Ricardo Wurmus
2017-10-13 21:10 ` Ricardo Wurmus
2017-11-07 10:57 ` Ludovic Courtès
2018-04-30 21:19 ` Ludovic Courtès
2019-01-29 10:07 ` Ricardo Wurmus
2017-09-25 8:43 ` Clément Lassieur
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=87k20nz18u.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=27476@debbugs.gnu.org \
--cc=help-guix@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.
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).