all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36754@debbugs.gnu.org
Subject: bug#36754: SSH connections to hydra-slave{1, 2, 3} fail during builds
Date: Tue, 23 Jul 2019 23:55:13 +0200	[thread overview]
Message-ID: <87pnm0bem6.fsf@elephly.net> (raw)
In-Reply-To: <87lfwo1lz0.fsf@gnu.org>


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

> Currently we have an SSH tunnel set up on berlin to connect to each of
> these machines via overdrive1.guixsd.org.  This setup proved to be
> robust in the past (we used it to connect to another build machine), so
> I suspect something’s wrong on “your” end of the network.  It’s hard to
> tell exactly what, though.

FWIW by the end of this week we should have the firewall changes
implemented so we can do without the SSH tunnel.

--
Ricardo

  reply	other threads:[~2019-07-23 21:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-21 23:56 bug#36754: New linux-libre failed to build on armhf on Berlin Mark H Weaver
2019-07-22 16:10 ` Ricardo Wurmus
2019-07-22 17:13 ` Mark H Weaver
2019-07-23 16:46   ` Marius Bakke
2019-07-23 17:33     ` bug#36754: SSH connections to hydra-slave{1, 2, 3} fail during builds (was: New linux-libre failed to build on armhf on Berlin) Mark H Weaver
2019-07-23 17:49       ` Mark H Weaver
2019-07-23 21:26         ` bug#36754: SSH connections to hydra-slave{1, 2, 3} fail during builds Ludovic Courtès
2019-07-23 21:55           ` Ricardo Wurmus [this message]
2019-08-01 15:39             ` Ricardo Wurmus
2019-07-24 11:09           ` Mark H Weaver
2019-07-24 14:56             ` Ludovic Courtès
2019-08-01 14:09               ` Marius Bakke
2019-08-01 16:37                 ` Mark H Weaver
2019-08-01 21:06                   ` Ricardo Wurmus
2019-08-07 14:30                     ` Ricardo Wurmus
2019-08-16 10:25                       ` Ludovic Courtès
2019-09-12  8:41                         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pnm0bem6.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=36754@debbugs.gnu.org \
    --cc=ludo@gnu.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 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.