Re^4: perl networking problem,no threads used

Hey, while we're all explaining, can you tell me why Corion and/or you haven't submitted a bug report to POE's request tracker queue? It's almost as if nobody actually cares whether bugs get fixed. :(

Anyway, POE's tests check a wide variety of features, including some things that are supported marginally in MSWin32 land. For all I know, the fork() tests are hanging but the networking tests pass fine. A detailed bug report sure would help, if that's not too much trouble.

Thanks!

-- Rocco Caputo - http://poe.perl.org/

Comment on Re^4: perl networking problem,no threads used

Replies are listed 'Best First'.
Re^5: perl networking problem,no threads used by bart (Canon) on Jan 12, 2007 at 11:41 UTC
What can we say, "the tests hang"? That doesn't seem to be very useful. I did try to investigate it further, and the weird thing is: if I run the hanging test (judging by the last message in the console) by itself, it runs flawlessly! So I assume it's actually the cleanup of one of the earlier tests that failed, for example a kill of a child process that didn't work because of platform differences. IIRC it was indeed in the test zone of launching child processes and stopping them again. I'm new to POE, so I'm nowhere familiar with the internals. But I promise one of these days I'll inspect it more closely while running the (edited) tests, to see exactly where it hangs.	[reply]
Re^5: perl networking problem,no threads used by Corion (Patriarch) on Jan 12, 2007 at 12:38 UTC
The report now lives as RT Ticket 24339. Thanks to bart for pointing out the discussion to me. As I don't use POE, I haven't undertaken an investigation as to why the test hangs, sorry.	[reply]