GNU bug report logs - #22582
25.0.90; package-test fail on w64

Previous Next

Full log

Message #17 received at 22582 <at> debbugs.gnu.org (full text, mbox):

From: Fabrice Popineau <fabrice.popineau <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 22582 <at> debbugs.gnu.org
Subject: Re: bug#22582: 25.0.90; package-test fail on w64
Date: Mon, 8 Feb 2016 11:04:49 +0100

[Message part 1 (text/plain, inline)]

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?


Fabrice


2016-02-07 21:50 GMT+01:00 Eli Zaretskii <eliz <at> gnu.org>:

> > From: Fabrice Popineau <fabrice.popineau <at> gmail.com>
> > Date: Sun, 7 Feb 2016 20:17:59 +0100
> > Cc: 22582 <at> debbugs.gnu.org
> >
> > The second problem is still there. Under Windows 10 and my setup, a
> 10049 error is reported
> > when trying to connect to http://0.0.0.0:8000/
>
> Thanks.  I guess it's something new with Windows 10, then.  (Error
> 10049 means "The requested address is not valid in its context.")
>
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.