Skip Menu |

This queue is for tickets about the Starlet CPAN distribution.

Report information
The Basics
Id: 103299
Status: patched
Priority: 0/
Queue: Starlet

People
Owner: Nobody in particular
Requestors: corsepiu [...] fedoraproject.org
Cc:
AdminCc:

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



Subject: Starlet-0.24 fails to build with Test::TCP >= 2.08
Date: Sat, 04 Apr 2015 06:26:56 +0200
To: bug-Starlet [...] rt.cpan.org
From: Ralf Corsépius <corsepiu [...] fedoraproject.org>
Hi, Starlet-0.24 fails to build from source with a testsuite failure with when using Test::TCP >= 2.08. ... t/10unix_domain_socket.t ... ok failed to listen:Address already in use at t/11multi-sockets.t line 15. t/11multi-sockets.t ........ Dubious, test returned 98 (wstat 25088, 0x6200) No subtests run Test Summary Report ------------------- t/11multi-sockets.t (Wstat: 25088 Tests: 0 Failed: 0) Non-zero exit status: 98 Parse errors: No plan found in TAP output ... The package built without problems w/ Test::TCP <= 2.08. Ralf
Thank you for reporting the issue. The problem has been fixed in Test::TCP 2.10. Also sent a bug report to perlbug@perl.org since I believe the cause of the problem is due to a bug in the Perl interpreter itself. On 2015-4月-04 土 00:30:47, corsepiu@fedoraproject.org wrote: Show quoted text
> Hi, > > Starlet-0.24 fails to build from source with a testsuite failure with > when using Test::TCP >= 2.08. > > ... > t/10unix_domain_socket.t ... ok > failed to listen:Address already in use at t/11multi-sockets.t line 15. > t/11multi-sockets.t ........ > Dubious, test returned 98 (wstat 25088, 0x6200) > No subtests run > Test Summary Report > ------------------- > t/11multi-sockets.t (Wstat: 25088 Tests: 0 Failed: 0) > Non-zero exit status: 98 > Parse errors: No plan found in TAP output > ... > > The package built without problems w/ Test::TCP <= 2.08. > > Ralf
From: ppisar [...] redhat.com
Dne Po 06.dub.2015 15:50:20, KAZUHO napsal(a): Show quoted text
> Thank you for reporting the issue. > > The problem has been fixed in Test::TCP 2.10.
It recurred with Test::TCP 2.15 again <https://github.com/tokuhirom/Test-TCP/issues/50>.