From: Robert Pluim <rpluim@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: EMBA (Emacs Gitlab CI build server) is now *public* available
Date: Tue, 05 Feb 2019 16:50:10 +0100 [thread overview]
Message-ID: <m2a7ja8cb1.fsf@gmail.com> (raw)
In-Reply-To: <o97q9r7j.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 05 Feb 2019 15:42:56 +0000")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Tue, 05 Feb 2019 15:58:43 +0100 Robert Pluim <rpluim@gmail.com> wrote:
>
> RP> Iʼve pushed changes to the failing tests under the assumption that
> RP> either that host doesnʼt have IPv6 support in its headers, or it has
> RP> no IPv6 stack running, but since I donʼt have any hosts like that, Iʼm
> RP> guessing quite a bit.
>
> I think this is an artifact of running inside Docker. It does IPv4 by
> default. According to the docs we can give the default docker0 bridge a
> local IPv6 address or globally routable IPv6 addresses (which we also
> have to confirm with the FSF sysadmins). I'm not sure what's better in
> the context of building and testing Emacs?
All the emacs IPv6 tests connect to localhost only, so definitely no
need for a globally routable address. We could probably get away with
just "::1" working.
Robert
prev parent reply other threads:[~2019-02-05 15:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 16:29 EMBA (Emacs Gitlab CI build server) is now available Ted Zlatanov
2018-12-31 17:54 ` Michael Albinus
2018-12-31 18:05 ` Ted Zlatanov
2019-01-01 12:08 ` Michael Albinus
2019-01-01 14:56 ` Ted Zlatanov
2019-01-01 16:51 ` Michael Albinus
2019-01-02 15:05 ` Justin Joseph Kaipada
2019-01-02 15:17 ` Michael Albinus
2019-01-04 11:52 ` Michael Albinus
2019-01-05 8:01 ` Toon Claes
2019-01-30 8:53 ` EMBA (Emacs Gitlab CI build server) is now *public* available Toon Claes
2019-01-30 9:46 ` Robert Pluim
2019-01-30 10:00 ` Michael Albinus
2019-01-30 11:23 ` Toon Claes
2019-01-30 12:13 ` Michael Albinus
2019-01-30 20:39 ` Ted Zlatanov
2019-02-05 12:50 ` Robert Pluim
2019-02-05 12:55 ` Michael Albinus
2019-02-05 14:58 ` Robert Pluim
2019-02-05 15:42 ` Ted Zlatanov
2019-02-05 15:50 ` Robert Pluim [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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2a7ja8cb1.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).