From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 19671@debbugs.gnu.org
Subject: bug#19671: Raw binary data in build log from substitute-binary
Date: Wed, 11 Feb 2015 10:41:55 +0100 [thread overview]
Message-ID: <87y4o4wzrw.fsf@gnu.org> (raw)
In-Reply-To: <87lhk93g9b.fsf@netris.org> (Mark H. Weaver's message of "Sat, 07 Feb 2015 10:14:56 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> Mark H Weaver <mhw@netris.org> writes:
>
>> While trying to install 'racket' using substitutes, several lines of the
>> form "substitute-binary: <binary garbage>" were output. See the
>> attachment for the precise output, captured via Emacs' shell mode.
>>
>> This was when running guix from git commit 2dfed64 on an i686 GSD
>> system.
>
> The same problem happened to me again, this time on git commit 710f3ce,
> while running 'guix system build'. I've attached another transcript.
>
> The binary junk is immediately followed (with no intervening newline) by
> the message:
>
> http://hydra.gnu.org/2zadn0b2kljwlsyarr3j5rz44yi2pvs3.narinfo' failed: 502, "Bad Gateway"
>
> This suggests that nginx had a problem fetching it from hydra-server on
> port 3000. Repeating the same command worked properly.
I don’t see how the binary garbage could reach the stdout of ‘guix
substitute-binary’. This happens when hydra.gnu.org is overloaded as
you suggest, so perhaps we have a connection closed unexpected or
something like that, but still.
Since this is the multithreaded ‘substitute-binary’, could there be
something fishy going on in wrt. threads?
Ludo’.
next prev parent reply other threads:[~2015-02-11 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 9:03 bug#19671: Raw binary data in build log from substitute-binary Mark H Weaver
2015-02-07 15:14 ` Mark H Weaver
2015-02-11 9:41 ` Ludovic Courtès [this message]
2015-03-23 9:49 ` Ludovic Courtès
2015-04-04 22:01 ` Ludovic Courtès
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=87y4o4wzrw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=19671@debbugs.gnu.org \
--cc=mhw@netris.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).