unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Philipp <p.stephani2@gmail.com>
Cc: 30700@debbugs.gnu.org
Subject: bug#30700: 27.0.50; Broken tests on macOS
Date: Sun, 06 Jan 2019 22:40:17 +0000	[thread overview]
Message-ID: <m2d0p99zqm.fsf@breton.holly.idiocy.org> (raw)
In-Reply-To: <20180319125913.GA22163@breton.holly.idiocy.org> (Alan Third's message of "Mon, 19 Mar 2018 12:59:13 +0000")

Alan Third <alan@idiocy.org> writes:

> On Sun, Mar 04, 2018 at 08:05:02PM +0100, Philipp wrote:
>> 
>> The following tests fail for me on macOS with a recent master build:
>> 
>> network-stream-tests:
>> 
>> Test echo-server-with-dns backtrace:
>>   make-network-process(:name "server" :server t :noquery t :family ipv
>>   make-server("p")
>>   (let* ((server (make-server (system-name))) (port (aref (process-con
>>   (closure (t) nil (let* ((server (make-server (system-name))) (port (
>>   ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
>>   ert-run-test(#s(ert-test :name echo-server-with-dns :documentation n
>>   ert-run-or-rerun-test(#s(ert--stats :selector (not (or (tag :expensi
>>   ert-run-tests((not (or (tag :expensive-test) (tag :unstable))) #f(co
>>   ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable)))
>>   ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
>>   eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
>>   command-line-1(("-L" ":." "-l" "ert" "-l" "lisp/net/network-stream-t
>>   command-line()
>>   normal-top-level()
>> Test echo-server-with-dns condition:
>>     (error "p/0 nodename nor servname provided, or not known")
>> 
>> The macOS firewall prevents creating the server here.  Probably we
>> should just skip this test on macOS.
>
> Are you sure that’s what’s going on? The other server tests appear to
> work. I would expect this one to fail on my set up because the DNS
> entry for my computer only has an IPv6 address, but this test seems to
> rely on IPv4.

Looking further into this, if I change ":family" in make-server, either
by removing it, or changing it to 'ipv6, I get the following:

  (file-error "make client process failed" "Connection refused" :name
  "foo" :buffer #<buffer *foo*<19>> :host "breton.holly.idiocy.org"
  :service ...)

which implies the server is being created, but then the client can't
connect. Looking at netstat I can't see the port.

Turning off the macOS firewall makes no difference to any tests.
-- 
Alan Third





  reply	other threads:[~2019-01-06 22:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-04 19:05 bug#30700: 27.0.50; Broken tests on macOS Philipp
2018-03-05 22:48 ` Glenn Morris
2018-03-19 12:59 ` Alan Third
2019-01-06 22:40   ` Alan Third [this message]
2019-04-17 18:56     ` Philipp Stephani
2019-04-17 19:25 ` Philipp Stephani
2019-10-09 14:13 ` Stefan Kangas
2019-11-11  1:52   ` Stefan Kangas

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=m2d0p99zqm.fsf@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=30700@debbugs.gnu.org \
    --cc=p.stephani2@gmail.com \
    /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).