all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: 22582@debbugs.gnu.org
Subject: bug#22582: 25.0.90; package-test fail on w64
Date: Mon, 08 Feb 2016 19:19:47 +0200	[thread overview]
Message-ID: <83bn7rqfv0.fsf@gnu.org> (raw)
In-Reply-To: <CAFgFV9NGjfWfFWL_G1gaRbYb2S5EdbvQDJnb27G1A+Xoa1wCAQ@mail.gmail.com> (message from Fabrice Popineau on Mon, 8 Feb 2016 11:04:49 +0100)

> From: Fabrice Popineau <fabrice.popineau@gmail.com>
> Date: Mon, 8 Feb 2016 11:04:49 +0100
> Cc: 22582@debbugs.gnu.org
> 
> If I run the package-test-server.py and I try to connect from a browser with
> http://0.0.0.0:8000/archive-contents, I get ERR_ADDRESS_INVALID.
> 
> But that I have the same error if I try to open:
> http://xx.xx.xx.xx:8000/archive-contents with xx.xx.xx.xx being my current IP address.
> 
> I get the file only if I connect to http://127.0.0.1:8000/archive-contents.
> 
> So I suspect that it is a default setting of the firewall in Windows 10.
> 
> The python server script 
> test/automated/data/package/package-test-server.py
> runs explicitly on 127.0.0.1, so why not using this address in the test?
> What does using 0.0.0.0 brings here in the package-test-update-archives-async test?

I don't know.  Perhaps someone else does.

Failing that, maybe we should just make the change and see who
hollers.





  reply	other threads:[~2016-02-08 17:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 14:25 bug#22582: 25.0.90; package-test fail on w64 Fabrice Popineau
2016-02-07 18:02 ` Eli Zaretskii
2016-02-07 19:17   ` Fabrice Popineau
2016-02-07 20:50     ` Eli Zaretskii
2016-02-08 10:04       ` Fabrice Popineau
2016-02-08 17:19         ` Eli Zaretskii [this message]
2017-02-25 17:58           ` npostavs

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=83bn7rqfv0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22582@debbugs.gnu.org \
    --cc=fabrice.popineau@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.