From: Ken Brown <kbrown@cornell.edu>
To: Achim Gratz <Stromeko@nexgo.de>, 23606@debbugs.gnu.org
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: bug#23606: 25.1.50; "localhost" vs. "127.0.0.1"
Date: Tue, 24 May 2016 14:35:17 -0400 [thread overview]
Message-ID: <b1bd8af3-ef48-89be-1d8b-132eb3f7b286@cornell.edu> (raw)
In-Reply-To: <87posbv0dk.fsf@Rainer.invalid>
On 5/24/2016 1:20 PM, Achim Gratz wrote:
> Ken Brown writes:
>> The test echo-server-nowait in test/lisp/net/network-stream-tests.el
>> fails on Cygwin, but it passes if I create the client process using
>> "127.0.0.1" instead of "localhost":
>
> This could be a case where it makes a difference if the IPv6 (::1) or
> IPv4 address is returned (first) for localhost. IIRC, Windows and
> up-to-date Linux prefer IPv6 by default. If so, it would likely be
> better to fix the parts of the code that assumes return of IPv4
> addresses only.
You're right. In the test in question, IPv4 is specified for the server but not for the client. The test passes on Cygwin if I specify IPv4 for the client also:
diff --git a/test/lisp/net/network-stream-tests.el b/test/lisp/net/network-stream-tests.el
index c9b7cc7..f30c92a 100644
--- a/test/lisp/net/network-stream-tests.el
+++ b/test/lisp/net/network-stream-tests.el
@@ -145,6 +145,7 @@ server-process-filter
:buffer (generate-new-buffer "*foo*")
:host "localhost"
:nowait t
+ :family 'ipv4
:service port)))
(should (eq (process-status proc) 'connect))
(while (eq (process-status proc) 'connect)
Glenn, does this also fix the problem on RHEL 7.2?
Ken
next prev parent reply other threads:[~2016-05-24 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 20:34 bug#23606: 25.1.50; "localhost" vs. "127.0.0.1" Ken Brown
2016-05-23 20:57 ` Glenn Morris
2016-05-23 21:00 ` Lars Ingebrigtsen
2016-05-23 22:30 ` Glenn Morris
2016-05-24 15:47 ` Lars Ingebrigtsen
2016-05-24 17:20 ` Achim Gratz
2016-05-24 18:35 ` Ken Brown [this message]
2016-05-24 19:19 ` Glenn Morris
2016-05-24 19:57 ` Ken Brown
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=b1bd8af3-ef48-89be-1d8b-132eb3f7b286@cornell.edu \
--to=kbrown@cornell.edu \
--cc=23606@debbugs.gnu.org \
--cc=Stromeko@nexgo.de \
--cc=larsi@gnus.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).