GNU bug report logs -
#22582
25.0.90; package-test fail on w64
Previous Next
Reported by: Fabrice Popineau <fabrice.popineau <at> gmail.com>
Date: Sun, 7 Feb 2016 14:27:02 UTC
Severity: normal
Tags: fixed
Found in version 25.0.90
Fixed in version 26.1
Done: npostavs <at> users.sourceforge.net
Bug is archived. No further changes may be made.
Full log
Message #20 received at 22582 <at> debbugs.gnu.org (full text, mbox):
> From: Fabrice Popineau <fabrice.popineau <at> gmail.com>
> Date: Mon, 8 Feb 2016 11:04:49 +0100
> Cc: 22582 <at> 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.
This bug report was last modified 8 years and 91 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.