From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Mathieu Othacehe <othacehe@gnu.org>,
Tom Fitzhenry <tom@tom-fitzhenry.me.uk>,
guix-sysadmin@gnu.org, Greg Hogan <code@greghogan.com>,
55848@debbugs.gnu.org
Subject: bug#55848: [cuirass] workers stalled
Date: Thu, 11 Aug 2022 16:06:42 +0200 [thread overview]
Message-ID: <87h72iub65.fsf_-_@gnu.org> (raw)
In-Reply-To: <87czd8ugl7.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 10 Aug 2022 19:55:49 +0200")
Hi,
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Ludovic Courtès <ludo@gnu.org> skribis:
>>
>>> guix-daemon is configured to use the default substitute URLs,
>>> https://ci.guix.gnu.org and https://bordeaux.guix.gnu.org, which we know
>>> are unreachable.
>>>
>>> I’ve theoretically addressed this here:
>>>
>>> https://git.savannah.gnu.org/cgit/guix/maintenance.git/commit/?id=99bd9dc9001d6bea7480a7ce0e0e10ff78adb787
>>> https://git.savannah.gnu.org/cgit/guix/maintenance.git/commit/?id=b0661cc7d6dd74b0aeac3b052a80a8a2fef2af9c
>>>
>>> I tried to reconfigure those boxes with ‘guix deploy’, but this is
>>> currently on hold because ci.guix has run out of inodes…
>>
>> Time passed and I had kinda forgotten about it, but the problem remains.
>
> I wrote this earlier:
>
>> They should be using the local IP instead of routing through the
>> internet, so /etc/hosts should contain an entry for
>>
>> 141.80.167.131 ci.guix.gnu.org
>
> So running the daemon with “--substitute-urls=http://10.0.0.1” should
> not be necessary.
Oh my bad, sorry for overlooking your message.
Explicitly going through http://10.0.0.1 is still desirable I think
because we avoid HTTPS altogether.
‘guix deploy’ is still running on berlin.guix and building things;
unfortunately I’m going AFK for a bit. I’ll pick it up later unless
someone takes care of it by then.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-08-11 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 15:31 bug#55848: [cuirass] workers stalled Mathieu Othacehe
2022-06-08 19:07 ` Greg Hogan
2022-06-11 10:44 ` Tom Fitzhenry
2022-06-12 13:33 ` Ludovic Courtès
2022-06-12 16:10 ` Ricardo Wurmus
2022-06-12 20:22 ` Ludovic Courtès
2022-08-10 13:46 ` bug#55848: AArch64 honeycomb machines aren’t building stuff Ludovic Courtès
2022-08-10 17:55 ` Ricardo Wurmus
2022-08-11 14:06 ` Ludovic Courtès [this message]
2022-08-29 13:30 ` bug#55848: AArch64 Honeycomb builders are inactive Ludovic Courtès
2022-06-19 2:07 ` bug#55848: [cuirass] workers stalled Tom Fitzhenry
2022-06-20 2:39 ` Maxim Cournoyer
2022-06-20 2:44 ` Tom Fitzhenry
2022-06-20 13:02 ` Maxime Devos
2022-06-21 5:32 ` Maxim Cournoyer
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=87h72iub65.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=55848@debbugs.gnu.org \
--cc=code@greghogan.com \
--cc=guix-sysadmin@gnu.org \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
--cc=tom@tom-fitzhenry.me.uk \
/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.