Front page | perl.perl5.porters |
Postings from October 2014
On Mon, Sep 29, 2014 at 9:42 AM, Paul "LeoNerd" Evans <leonerd@leonerd.org.uk> wrote: > https://rt.cpan.org/Ticket/Display.html?id=98976 > > t/22timeout.t is failing on MSWin32, and as is typical with such > failures I have no idea why nor have direct access to any resource to > test this with. > > Can anyone offer assistance? This is a dual-life core module so it's > currently breaking blead. Haven't had a chance to fire up a Windows build, but FWIW it also fails on VMS. Changing IO::Socket::IP to IO::Socket::INET makes it work fine. As does removing the timeout. The symptom is different from Windows; rather than an invalid file descriptor the connect attempt actually does fail with "connection timed out." Increasing the timeout just makes it wait longer before failing. Don't know why yet, but given the above points I'd suspect something about the way the timeout is being set up in IO::Socket::IP. Hope to debug further at some point, and of course there's no guarantee the underlying issue is the same as on Windows. > Additionally, I keep thinking it would be nice if we had a more formal > request mechanism for "I need help with $^O" for various values, where > the requester doesn't have access to an OS they need to fix things on, > or a domain expert with some knowledge to help. Given the rag-tag, informal nature of the domain expertise you're looking for, I'm not sure any formal mechanism could really work. People tend to work on the things that interest them and it's always been a problem to find enough people interested in chasing test failures on Win32. You might get better results from one of the mailing lists with "win32" in the name than from p5p.Thread Previous | Thread Next