On Sun, 15 Aug 2004, Stas Bekman wrote: > Markus Wichitill wrote: > > Stas Bekman wrote: > > > >>> t\filter\in_bbs_inject_header.t always succeeds when run as part of > >>> the whole "nmake new" run, and only sometimes crashes Apache when run > >>> alone, which was only uncovered by last night's SMOKE run. > >> and post the output (client + error_log) of that last run. Thanks. > > > > > > C:\Dev\src\modperl-2.0-test>c:\dev\test\perl\bin\perl t\TEST -v -run > > t/filter/in_bbs_inject_header.t > > t\filter\in_bbs_inject_header....# connecting to localhost:8545 > > 1..36 > > # Running under perl version 5.008005 for MSWin32 > > # Current time local: Mon Aug 16 01:51:33 2004 > > # Current time GMT: Sun Aug 15 23:51:33 2004 > > # Using Test.pm version 1.25 > > # Using Apache/Test.pm version 1.13 > > request has failed (the response code was: 500) > > see t/logs/error_log for more details > > dubious > > Test returned status 9 (wstat 2304, 0x900) > > DIED. FAILED tests 1-36 > > Failed 36/36 tests, 0.00% okay > > Failed Test Stat Wstat Total Fail Failed List of > > Failed > > ------------------------------------------------------------------------------- > > > > t\filter\in_bbs_inject_header.t 9 2304 36 72 200.00% 1-36 > > Failed 1/1 test scripts, 0.00% okay. 36/36 subtests failed, 0.00% okay. > > [ error] error running tests (please examine t\logs\error_log) > > > > Nothing interesting in the log: > > > > [...] > > [Mon Aug 16 01:51:29 2004] [debug] child.c(684): Child 1160: Worker > > thread 49 starting. > > [eof] > > Right, a debugger is needed here. > > The fact is that it fails on its own but not when running after some other > tests tells me that something happens that helps the test. It's probably > not easy as there are many tests but if you do a binary search you may > find relatively quickly what specific test (or a combination of) makes it > successful. That what t/SMOKE would have done for you, but here were are > trying to find the successful sequence, not the failing one. > > >> Incidently, this module does the same as this test and more: > >> http://apache.org/~stas/Apache-Filter-HTTPHeadersFixup-0.04.tar.gz > >> Could you give it a try? Make sure that you first build and install > >> the latest mod_perl cvs (i just checked it some A-T fix). Thanks. > > > > > > Crashes on t\manip\out_append.t #1, with no useful error_log either. > > Good to hear that. At least the error is consistent. > > The fact is that it fails on its own but not when running after some other > tests tells me that something happens that helps the test. > > > Maybe we should just wait until Randy is back home, unless someone can > > give me VC6 debugging advice. > > We can always exclude some tests from the release and resolve them later, > if that is not resolved by the release time.
Is this a crash, in the sense that a pop-up window appears with a message about, eg, an access violation? Or is it "just" a regular server error? If the latter, what one can do to run the debugger is to put a pause in the test to give you time to launch VC++ and attach the debugger to the Apache process before the error happens. I'll take a look at this when I get back on the weekend. -- best regards, randy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
