From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: help-guix mailing list <help-guix@gnu.org>
Subject: Re: Guix substitute timeout
Date: Mon, 02 Sep 2019 14:11:56 +0200 [thread overview]
Message-ID: <87h85uaodv.fsf@gnu.org> (raw)
In-Reply-To: <87sgpgfkp4.fsf@cbaines.net> (Christopher Baines's message of "Sun, 01 Sep 2019 10:08:07 +0100")
Hi Chris!
Christopher Baines <mail@cbaines.net> skribis:
> I'm unsure how well the substituter copes with unreliable network
> connections, anecdotally it seems to often hang indefinitely.
How often?
I experienced it at some point last year but the problem vanished soon
after I reported it here: <https://issues.guix.gnu.org/issue/31925>.
If you can reproduce it, could you try to get a C backtrace of ‘guix
substitute’, as well as the output of ‘guix’ to see if it’s fetching
gzip or lzip stuff, and the process sub-tree?
> Looking at the code [1], there is some code that looks like it would
> cancel the substitution after some amount of time, but it also looks to
> be disabled (as #:timeout? is #f when fetch is called).
That comes from commit 2207f73156e144a9349e4d395d5049119b67a896 from
2013 (!), when hydra.gnu.org was so slow and (I think) we’d rather not
time out too quickly while fetching a substitute or we’d never fetch
anything. Good times…
We could probably enable it, though it should be a not-too-short
timeout.
Thoughts?
Ludo’.
prev parent reply other threads:[~2019-09-02 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 9:08 Guix substitute timeout Christopher Baines
2019-09-02 12:11 ` Ludovic Courtès [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
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=87h85uaodv.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=mail@cbaines.net \
/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).