unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Mathieu Othacehe <othacehe@gnu.org>,
	guix-sysadmin@gnu.org, 55848@debbugs.gnu.org,
	Greg Hogan <code@greghogan.com>,
	Tom Fitzhenry <tom@tom-fitzhenry.me.uk>
Subject: bug#55848: [cuirass] workers stalled
Date: Sun, 12 Jun 2022 18:10:00 +0200	[thread overview]
Message-ID: <871qvt2701.fsf@elephly.net> (raw)
In-Reply-To: <87bkuyvwf0.fsf@gnu.org>


Ludovic Courtès <ludo@gnu.org> writes:

> Hi,
>
> (+Cc: guix-sysadmin)
>
> Tom Fitzhenry <tom@tom-fitzhenry.me.uk> skribis:
>
>>>From following the builds on http://ci.guix.gnu.org/workers , many
>> (all?) builds are failing on the following workers:
>>
>> * grunewald
>> * kreuzberg
>> * pankow
>>
>> The builds are failing with the same error:
>>
>> "substitute: updating substitutes from 'https://ci.guix.gnu.org'...
>> 0.0%guix substitute: error: TLS error in procedure 'handshake': Error in
>> the pull function."
>
> On these machines, https://ci.guix.gnu.org (among other) is unavailable
> for some reason (firewall I guess):

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

(We have the same entry on the other build nodes hosted at the MDC.)

“guix deploy” did not work on these nodes due to a serious problem: they
were given *some* x86_64 binaries to execute, so deployed systems were
unbootable.  Since we don’t have a serial interface through which you
could debug this remotely, please make sure not to deploy a broken
system.  I’d like to avoid trips to the data centre.

-- 
Ricardo




  reply	other threads:[~2022-06-12 16:16 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 [this message]
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           ` bug#55848: [cuirass] workers stalled Ludovic Courtès
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

  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=871qvt2701.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=55848@debbugs.gnu.org \
    --cc=code@greghogan.com \
    --cc=guix-sysadmin@gnu.org \
    --cc=ludo@gnu.org \
    --cc=othacehe@gnu.org \
    --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 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).