From: "Ludovic Courtès" <ludo@gnu.org>
To: Attila Lendvai <attila@lendvai.name>
Cc: 57978@debbugs.gnu.org
Subject: bug#57978: the fallback machanism for substitute servers doesn't work?
Date: Thu, 22 Sep 2022 11:47:56 +0200 [thread overview]
Message-ID: <875yhfivub.fsf@gnu.org> (raw)
In-Reply-To: <GH6ClCMfJDFA4PobJSLUVueUqLEv5WxDfh-ekx5Cfu5sUiZM3pNUX_vEr00tR4vg7Z2x3L22NRmWl6HRGseLa8MgT3O9EpUlpOo2MfznfOY=@lendvai.name> (Attila Lendvai's message of "Wed, 21 Sep 2022 13:11:06 +0000")
Hi,
Attila Lendvai <attila@lendvai.name> skribis:
> guix substitute: warning: ci.guix.gnu.org: connection failed: No route to host
> qemu-minimal-7.1.0-doc 3.4MiB 876.6MiB/s 00:00 [##################] 100.0%
> guix substitute: error: connect*: No route to host
> substitution of /gnu/store/7czrnkybr466v69wdj6i2sn6vpsg0ks3-cdrkit-libre-1.1.11 failed
> guix system: error: corrupt input while restoring archive from #<closed: file 7f37458bd000>
I observed the same yesterday when ci.guix was down.
Note that the following command, where 203.* is unroutable, does not
reproduce it:
guix build --substitute-urls="http://203.0.113.1 https://ci.guix.gnu.org" \
--no-grafts pandoc # pick a package not in store
So I believe what we experienced yesterday goes along these lines:
1. We had cached narinfos for ci.guix available locally so the daemon
assumed it could go ahead and download from ci.guix;
2. When ‘guix substitute --substitute’ when to download stuff from
ci.guix, which it assumed was possible because there was a valid
narinfo for that, it didn’t handle the connection failure. (The
same happens if you get, say, 404 while substituting even though
you have a valid substitute at hand.)
Trying to come up with a fix…
Ludo’.
next prev parent reply other threads:[~2022-09-22 10:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 13:11 bug#57978: the fallback machanism for substitute servers doesn't work? Attila Lendvai
2022-09-21 20:43 ` zimoun
2022-09-22 9:47 ` Ludovic Courtès [this message]
2022-09-23 6:16 ` bug#57978: [PATCH 0/2] Retry nar downloads upon failure Ludovic Courtès
2022-09-28 21:24 ` bug#57978: bug#58017: " Ludovic Courtès
2022-09-23 6:19 ` bug#57978: [PATCH 1/2] substitute: Split nar download Ludovic Courtès
2022-09-23 6:19 ` bug#57978: [PATCH 2/2] substitute: Retry downloading when a nar is unavailable Ludovic Courtès
2022-09-23 8:17 ` [bug#58017] " zimoun
2022-09-24 16:20 ` Ludovic Courtès
2022-09-24 1:57 ` bug#57978: [bug#58017] " Maxime Devos
2022-09-24 16:22 ` Ludovic Courtès
2022-09-24 17:18 ` bug#57978: " Maxime Devos
2022-09-23 7:56 ` bug#57978: [PATCH 1/2] substitute: Split nar download zimoun
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=875yhfivub.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=57978@debbugs.gnu.org \
--cc=attila@lendvai.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.