Skip Menu |
 

This queue is for tickets about the Crypt-SSLeay CPAN distribution.

Report information
The Basics
Id: 30985
Status: resolved
Priority: 0/
Queue: Crypt-SSLeay

People
Owner: nanis [...] runu.moc.invalid
Requestors: adam.prime [...] utoronto.ca
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.57
Fixed in: (no value)



Subject: make test fails if 127.0.0.1:443 is in use.
If you attempt to build Crypt::SSLeay on a machine where port 443 is bound on 127.0.0.1 make test fails like this: t/01-connect.... # Failed test 'Net::SSL->new' t/01-connect....NOK 1/8# in t/01-connect.t at line 25. # SSL negotiation failed: at t/01-connect.t line 11 # at t/01-connect.t line 11 # ; Interrupted system call at t/01-connect.t line 11 # ; Interrupted system call at t/01-connect.t line 11 # ; Interrupted system call at t/01-connect.t line 11 t/01-connect....ok 2/8# Looks like you failed 1 test of 8. t/01-connect....dubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 1 Failed 1/8 tests, 87.50% okay (less 7 skipped tests: 0 okay, 0.00%) t/02-live.......ok 1/4# config on linux # ssl OpenSSL 0.9.8 in /usr # lib -L/usr/lib -lssl -lcrypto -lgcc # inc -I/usr/include/openssl # cc i686-pc-linux-gnu-gcc When I kill the process bound to port 443, make test passes fine. Ideally, a more explicit statement of what's causing the make test failure would probably clue people in as to how to fix it, or better yet, bind a random port instead of 443.
Subject: Re: [rt.cpan.org #30985] make test fails if 127.0.0.1:443 is in use.
Date: Tue, 27 Nov 2007 09:50:18 +0100
To: bug-Crypt-SSLeay [...] rt.cpan.org
From: David Landgren <david [...] landgren.net>
Download (untitled) / with headers
text/plain 1.9k
Adam Prime via RT wrote: Show quoted text
> Mon Nov 26 14:07:29 2007: Request 30985 was acted upon. > Transaction: Ticket created by APRIME > Queue: Crypt-SSLeay > Subject: make test fails if 127.0.0.1:443 is in use. > Broken in: 0.57 > Severity: Normal > Owner: Nobody > Requestors: adam.prime@utoronto.ca > Status: new > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=30985 > > > > If you attempt to build Crypt::SSLeay on a machine where port 443 is > bound on 127.0.0.1 make test fails like this: > > t/01-connect.... > # Failed test 'Net::SSL->new' > t/01-connect....NOK 1/8# in t/01-connect.t at line 25. > # SSL negotiation failed: at t/01-connect.t line 11 > # at t/01-connect.t line 11 > # ; Interrupted system call at t/01-connect.t line 11 > # ; Interrupted system call at t/01-connect.t line 11 > # ; Interrupted system call at t/01-connect.t line 11 > t/01-connect....ok 2/8# Looks like you failed 1 test of 8. > t/01-connect....dubious > Test returned status 1 (wstat 256, 0x100) > DIED. FAILED test 1 > Failed 1/8 tests, 87.50% okay (less 7 skipped tests: 0 okay, 0.00%) > t/02-live.......ok 1/4# config on linux > # ssl OpenSSL 0.9.8 in /usr > # lib -L/usr/lib -lssl -lcrypto -lgcc > # inc -I/usr/include/openssl > # cc i686-pc-linux-gnu-gcc > > When I kill the process bound to port 443, make test passes fine. > Ideally, a more explicit statement of what's causing the make test > failure would probably clue people in as to how to fix it, or better > yet, bind a random port instead of 443.
You are my hero! I've been wondering about these failures but hadn't come up with a diagnosis. When I took over maintenance there were no tests at all worth speaking of, and I wanted to try and improve the situation. This is one of the tests I added that proved to be problematic. I'll cook something up and push a new release out the door. Thank-you very much for taking the time to write, it is most appreciated. David
From: dland [...] cpan.org
Download (untitled) / with headers
text/plain 1.3k
On Mon Nov 26 14:07:29 2007, APRIME wrote: Show quoted text
> If you attempt to build Crypt::SSLeay on a machine where port 443 is > bound on 127.0.0.1 make test fails like this: > > t/01-connect.... > # Failed test 'Net::SSL->new' > t/01-connect....NOK 1/8# in t/01-connect.t at line 25. > # SSL negotiation failed: at t/01-connect.t line 11 > # at t/01-connect.t line 11 > # ; Interrupted system call at t/01-connect.t line 11 > # ; Interrupted system call at t/01-connect.t line 11 > # ; Interrupted system call at t/01-connect.t line 11 > t/01-connect....ok 2/8# Looks like you failed 1 test of 8. > t/01-connect....dubious > Test returned status 1 (wstat 256, 0x100) > DIED. FAILED test 1 > Failed 1/8 tests, 87.50% okay (less 7 skipped tests: 0 okay,
0.00%) Show quoted text
> t/02-live.......ok 1/4# config on linux > # ssl OpenSSL 0.9.8 in /usr > # lib -L/usr/lib -lssl -lcrypto -lgcc > # inc -I/usr/include/openssl > # cc i686-pc-linux-gnu-gcc > > When I kill the process bound to port 443, make test passes fine. > Ideally, a more explicit statement of what's causing the make test > failure would probably clue people in as to how to fix it, or better > yet, bind a random port instead of 443.
Hello, I have addressed this problem in 0.57_01. If you want to take it for a spin you are more than welcome. If no errors crop up this week I'll be releasing 0.58 this weekend. Thanks, David
Download (untitled) / with headers
text/plain 382b
Hello: I am closing this issue because 0.57_01 contains a patch for this issue. I am also working on clearing the rest of the RT queue so 0.58 can be released soon. The most recent developer release is 0.57_04 available at: http://search.cpan.org/~nanis/Crypt-SSLeay-0.57_04/ I would appreciate it if you can test it and report any problems you encounter. Thank you. -- Sinan
Download (untitled) / with headers
text/plain 1.1k
On Fri Aug 13 11:30:53 2010, NANIS wrote: Show quoted text
> Hello: > > I am closing this issue because 0.57_01 contains a patch for this issue. > > I am also working on clearing the rest of the RT queue so 0.58 can be > released soon. The most recent developer release is 0.57_04 available at: > > http://search.cpan.org/~nanis/Crypt-SSLeay-0.57_04/ > > I would appreciate it if you can test it and report any problems you > encounter. > > Thank you.
looks good: adam@pooptop /tmp/Crypt-SSLeay-0.57_04 $ netstat -an | grep 443 tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN adam@pooptop /tmp/Crypt-SSLeay-0.57_04 $ make test PERL_DL_NONLAZY=1 /usr/bin/perl5.8.8 "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/00-basic.t .... ok t/01-connect.t .. ok t/02-live.t ..... 1/4 # config on linux # ssl OpenSSL 0.9.8o in /usr; # lib -L/usr/lib -lssl -lcrypto -lgcc # inc -I/usr/include # cc x86_64-pc-linux-gnu-gcc t/02-live.t ..... ok All tests successful. Files=3, Tests=24, 2 wallclock secs ( 0.04 usr 0.00 sys + 0.41 cusr 0.05 csys = 0.50 CPU) Result: PASS Adam
Download (untitled) / with headers
text/plain 1.2k
Hello Adam: Thank you for checking it out. -- Sinan On Fri Aug 13 12:19:25 2010, APRIME wrote: Show quoted text
> On Fri Aug 13 11:30:53 2010, NANIS wrote:
> > Hello: > > > > I am closing this issue because 0.57_01 contains a patch for this issue. > > > > I am also working on clearing the rest of the RT queue so 0.58 can be > > released soon. The most recent developer release is 0.57_04
available at: Show quoted text
> > > > http://search.cpan.org/~nanis/Crypt-SSLeay-0.57_04/ > > > > I would appreciate it if you can test it and report any problems you > > encounter. > > > > Thank you.
> > looks good: > > adam@pooptop /tmp/Crypt-SSLeay-0.57_04 $ netstat -an | grep 443 > tcp 0 0 0.0.0.0:443 0.0.0.0:* > LISTEN > adam@pooptop /tmp/Crypt-SSLeay-0.57_04 $ make test > PERL_DL_NONLAZY=1 /usr/bin/perl5.8.8 "-MExtUtils::Command::MM" "-e" > "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t > t/00-basic.t .... ok > t/01-connect.t .. ok > t/02-live.t ..... 1/4 # config on linux > # ssl OpenSSL 0.9.8o in /usr; > # lib -L/usr/lib -lssl -lcrypto -lgcc > # inc -I/usr/include > # cc x86_64-pc-linux-gnu-gcc > t/02-live.t ..... ok > All tests successful. > Files=3, Tests=24, 2 wallclock secs ( 0.04 usr 0.00 sys + 0.41 cusr > 0.05 csys = 0.50 CPU) > Result: PASS > > Adam


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.