On Thu, 20 May 2004, Steve Hay wrote: > Randy Kobes wrote: > > >On Thu, 20 May 2004, Geoffrey Young wrote: > > > >>a release candidate for mod_perl 1.99_14 is now available for testing. > >> > >> > >Hi Geoff, > > On Win32 (perl-5.8.3, ActivePerl 809 compatible), with > >Apache/2.0.49, there's a problem (often) in starting the > >tests, due to ThreadsPerChild being set too low (Steve, > >do you still find this?). This diff > > > >=================================================================== > >Index: Apache-Test/lib/Apache/TestConfig.pm > >=================================================================== > >RCS file: /home/cvs/httpd-test/perl-framework/Apache-Test/lib/Apache/TestConfig.pm,v > >retrieving revision 1.222 > >diff -u -r1.222 TestConfig.pm > >--- Apache-Test/lib/Apache/TestConfig.pm 16 Apr 2004 20:29:23 -0000 1.222 > >+++ Apache-Test/lib/Apache/TestConfig.pm 20 May 2004 06:11:47 -0000 > >@@ -1878,7 +1878,7 @@ > > </IfDefine> > > > > <IfModule mpm_winnt.c> > >- ThreadsPerChild 20 > >+ ThreadsPerChild 25 > > MaxRequestsPerChild 0 > > </IfModule> > > > >=========================================================================== > >allows the tests to start for me. > > > Not this one again! We've been here several times before -- see > http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=108296767420298&w=2. > > The patch above is fine if you think it is worth applying after all > (given that Apache 2.0.50 isn't out yet).
I agree - I think Geoff's suggestion of applying it and marking it for future back-compatibility checks is a good one. [ ... ] > The bad news is that on my setup (Apache 2.0.49, Perl 5.8.4) I haven't > yet seen the mp2 test suite run properly yet. (The same Apache/Perl > combination worked fine with 1.99_13.) > > When running "nmake test" I usually get t\compat\send_fd.t and > t\directive\setupenv.t failing like this: > > t\compat\send_fd........................response had protocol HTTP/0.9 > (headers not sent?) at t\compat\send_fd.t line 15 > t\compat\send_fd........................dubious > Test returned status 9 (wstat 2304, 0x900) > DIED. FAILED tests 1-3 > Failed 3/3 tests, 0.00% okay > > t\directive\setupenv....................response had protocol HTTP/0.9 > (headers not sent?) at t\directive\setupenv.t line 12 > t\directive\setupenv....................dubious > Test returned status 9 (wstat 2304, 0x900) > DIED. FAILED tests 1-3 > Failed 3/3 tests, 0.00% okay > > but they both pass OK when I run them manually via t/TEST. I also saw this (with 5.8.3), but didn't have time to look further (I will tonight). I also find they work OK run individually, or even as a group: perl t/TEST directive perl t/TEST compat > I then have "nmake test" sometimes failing completely on t\directive\pod > (Apache.exe throws up a popup Application Error and crashes). I haven't seen this, but as you say, some of these problems are occasional. > Other times that test runs OK, but then it hangs on > t\error\runtime.t. If I kill that test then rest of the > tests complete without error. I also get it hanging on error/runtime.t, without anything useful in the error log. What might be an idea is to skip this test for Win32 for this particular release, and look at it in the next development cycle. -- best regards, randy -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
