issue installing IO-Socket-SSL

perlknight has asked for the wisdom of the Perl Monks concerning the following question:

fellow monks I am trying to install IO::Socket::SSL, it's failing the make test stage, see below:

t/nonblock.........FAILED tests 10, 13, 26                            
+       
        Failed 3/27 tests, 88.89% okay
t/readline.........ok                                                 
+       
t/sessions.........ok                                                 
+       
t/startssl.........ok                                                 
+       
t/sysread_write....ok                                                 
+       
Failed Test  Stat Wstat Total Fail  Failed  List of Failed
----------------------------------------------------------------------
+---------
t/nonblock.t               27    3  11.11%  10 13 26
Failed 1/11 test scripts, 90.91% okay. 3/175 subtests failed, 98.29% o
+kay.
make: *** [test_dynamic] Error 29
[download]

Does anyone know what the error above mean and how can I resolve it? Most importantly, could I skip it and just do a make install? This is a pre-req to www mechanize, I want to use www mechanize to test a website, loging into it, test a query or two through the website and get some response statistic for it. Thanks.

Comment on issue installing IO-Socket-SSL Download Code

Replies are listed 'Best First'.

Re: issue installing IO-Socket-SSL
by grinder (Bishop) on Feb 26, 2007 at 18:17 UTC

To get a better idea about what exactly is failing, you can go directly to the build directory and run prove on the test script in question (assuming you're using the CPAN shell):

CPAN> look IO-Socket-SSL
$ prove -vb t/nonblock
$ exit
[download]

It may just be that it's trying to do something for which you don't have the required privileges, or something similar. If you know you won't be doing any work with SSL sites, you can safely force the install with (again, under the CPAN shell):

  force install IO::Socket::SSL
[download]

CPANPLUS has a similar mechanism to force the installation despite a test failure. Still, once you know exactly what test is failing and why, you may be able to do something about in order to get a clean bill of health. Otherwise if you get odd results later on, you can never be sure that it wasn't those tests that failed, which were warning you about something real.

• another intruder with the mooring in the heart of the Perl

[reply]
[d/l]
[select]


Come for the quick hacks, stay for the epiphanies.
	PerlMonks