Stas Bekman wrote:
Steve Hay wrote:
No, it's something in the mp2 test setup. If I just start my installed Apache2/mp2 setup then I get two Apache.exe's as expected. I'll try to see what the difference is.
Got it. We made an exception for Win32 to always run in one-process mode because otherwise we couldn't relaibly stop both the parent and child processes. See the call to Win32::Process::Create() in Apache::TestServer::start().
It does have the undesirable side-effect that we have seen in this thread, though, namely that if one test causes the single Apache.exe process to exit for whatever reason then all subsequent tests will fail since they now have no server to connect to :(
I can't really intelligently comment on this one, since I don't know if it's possible to rework that code to allow win32 spawn more than 1 proc :(
It's easy to start >1 process -- just don't force the $one_process option into the start $cmd! The problem IIRC was trying to stop them later. I think if the user CTRL+C's the test suite then only the parent was stopped, leaving the child still running, but I need to look back over the archives to see exactly what the problem was.
sorry, I've meant to somehow do the whole thing, start > 1 and stop them all of course.
what would be nice is to at least somehow abort the test suite, if there is no server running.
That's an idea worth looking into sometime.
I'll put that on the todo list.
-- __________________________________________________________________ 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]
