![]() |
|
Pathologically Eclectic Rubbish Lister | |
PerlMonks |
Re^3: Why does Test-WWW-Mechanize-Catalyst-0.55\t\multi_content_type.t hang on win32?by Corion (Pope) |
on Oct 10, 2011 at 15:26 UTC ( #930665=note: print w/replies, xml ) | Need Help?? |
Without looking further into this - my experience with fork() and sockets on Windows has led me to always spawn external processes (that is, HTTP servers) for module self-testing instead. Launching an external process via pipe-open works for HTTP::Server::Simple, WWW::Mechanize, WWW::Mechanize::Firefox and WWW::Mechanize::Shell. I would not bother with investigating why fork and sockets don't interact like on Unix, because the fork-emulation never handled that well anyway.
In Section
Seekers of Perl Wisdom
|
|