in reply to Re: LWP::Simple not installing on MAC OS Mojava
in thread LWP::Simple not installing on MAC OS Mojava

Hi stevieb,

Thank you for your advice, I had been using perlbrew in BASH but have recently changed to ZSH and it took me a while to realise I needed to change the $PATH to access perlbrew.

I have installed perlbrew and CPANM and tried again to install LWP::Simple. However, an error till occurs, even when I force the installation and in the .cpanm/work/........./build.log I get the same error:

t/00-report-prereqs.t .......... ok t/10-attrs.t ................... ok # Some tests for the PUT method can only be run on # HTTP::Request version 6.07 or higher. # If your version isn't good enough, we'll skip those. # Your version is 6.18 and that's good enough t/base/default_content_type.t .. ok t/base/protocols.t ............. ok # Failed test '404 on fake nntp url' # at t/base/protocols/nntp.t line 12. # got: '500' # expected: '404' # Looks like you failed 1 test of 1. t/base/protocols/nntp.t ........ Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests t/base/proxy.t ................. ok t/base/simple.t ................ ok t/base/ua.t .................... ok t/base/ua_handlers.t ........... ok t/leak/no_leak.t ............... ok t/local/autoload-get.t ......... ok t/local/autoload.t ............. ok

Replies are listed 'Best First'.
Re^3: LWP::Simple not installing on MAC OS Mojava
by Anonymous Monk on Mar 05, 2019 at 02:44 UTC

    I get the same error:

    So why dont you install the module already?

    A failing test does not prevent installation

      Sorry, I am new to perl and modules in particular. Could you advise how to install around the test failures? Currently I am using perlbrew and CPANM there another way you reccomend?

        You're doing all the right things (perlbrew, cpanm). The failing test you experienced was due to an outage to the underlying infrastructure. I appreciate that if you are just starting out it's hard to know which tests are OK to skip, and what are things you should genuinely be concerned with. You can evaluate these on a test by test basis, however should you wish to skip tests, cpanm has options: -n/--notest to skip tests all together, -f/--force to force the installation regardless of test failure.