Closed saberworks closed 9 years ago
I spent some time this morning looking into this further. There are also failures in this test reported on cpantesters, although the exact message is different. I found that the issue is caused by my host being behind an HTTP proxy. This is because the host doesn't have direct access to the internet. I used the following command to set up the proxy servers for cpan:
o conf init /proxy/
However, it is required to set the no_proxy value to include "localhost" otherwise the tests (using LWP) try to go through the http proxy to hit "localhost:
It would be nice if the test could detect whether it's going through a proxy, and if so, don't go through the proxy for the localhost connections. If not, at least an option to disable the server tests would be helpful.
On Tue, Apr 14, 2015 at 11:17 AM, saberworks notifications@github.com wrote:
It would be nice if the test could detect whether it's going through a proxy, and if so, don't go through the proxy for the localhost connections. If not, at least an option to disable the server tests would be helpful.
Regardless of whether there is a proxy, the tests should never need to contact the network. So can we just always override the proxy settings during testing?
Thanks for researching this. It has been eluding me for some time.
It seems reasonable to me. Instead of messing with environment variables I think you can use no_proxy() method on LWP directly.
This is the same as #176.
no proxy in play on my local machine, as a test, i disabled network and get several test suite failures:
all trying to connect to meta.stratopan.com:80 and www.cpan.org:80
my understanding is we need the following:
Those are release tests, generally not executed by end users. So those aren't really related to this issue.
This was fixed and released as Pinto-0.09999.
I installed perl 5.20.2 from source. Then I updated cpan using install CPAN, reload CPAN. Then I attempted to install Pinto. All the dependencies installed correctly with no failing tests or weird output. Then when it's testing Pinto itself, I get this test failure: