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

Previous Next

Full log

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

From: npostavs <at> users.sourceforge.net
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 22582 <at> debbugs.gnu.org, Fabrice Popineau <fabrice.popineau <at> gmail.com>
Subject: Re: bug#22582: 25.0.90; package-test fail on w64
Date: Sat, 25 Feb 2017 12:58:55 -0500

tags 22582 fixed
close 22582 26.1
quit

Eli Zaretskii <eliz <at> gnu.org> writes:

>> 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.

Done [1: 546d30ed14].

1: 2017-02-25 12:56:09 -0500 546d30ed1400d5a434886790a102bd37ec852919
  Don't use IP 0.0.0.0 for package test server (Bug#22582)

Previous Next

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