Randy Kobes wrote: [...]
I tried "perl t/SMOKE -verbose=1" and it makes no difference.
it's a problem inside t/SMOKE which invokes t/TEST internally.
It kicks off an Apach.exe which eats a bit of CPU for a short while and then everything goes quiet. Apache.exe stays sitting there, but doesn't seem to do anything else. I left it for nearly 2 hours and nothing happened.
The problem here I believe is the use of pipes to launch the tests. I'm working on, for Win32, the use of Win32::Process instead - it's almost working, in that I can get the server to start up and run, but there's a couple of things to iron out, which hopefully won't take long.
No, no, no, is it possible to keep the win32-specific code away, it makes the code totally unreadable and unmaintainable :( Randy, how about using IPC::Run, which seems to work fine everywhere. I don't mind t/SMOKE to depend on optional modules, which we didn't want for t/TEST.
p.s. sorry for being grumpy about win32, it's certainly not your fault.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
