On Thu, Jun 24, 2004 at 02:35:39PM -0400, William McKee wrote: > On Thu, Jun 24, 2004 at 09:30:29AM -0400, Geoffrey Young wrote: > > please take the time to excercise the candidate through all your existing > > applications that use Apache-Test and report back successes or failures. > > Looks good for me.
Ooops, spoke too soon again. I'm still having problems with TestRun.pm in Windows XP. Here's the output: [Thu Jun 24 17:21:56 2004] [error] [client 127.0.0.1] Statement unlikely to be reached at c:\TigerCub\perl5\5.8.3/Apache/TestRun.pm line 669. Compilation failed in require at c:\TigerCub\perl5\5.8.3/Apache/TestServer.pm line 25. BEGIN failed--compilation aborted at c:\TigerCub\perl5\5.8.3/Apache/TestServer.pm line 25. Compilation failed in require at c:\TigerCub\perl5\5.8.3/Apache/TestConfig.pm line 51. BEGIN failed--compilation aborted at c:\TigerCub\perl5\5.8.3/Apache/TestConfig.pm line 51. Compilation failed in require at c:\TigerCub\perl5\5.8.3/Apache/Test.pm line 23. BEGIN failed--compilation aborted at c:\TigerCub\perl5\5.8.3/Apache/Test.pm line 23. Compilation failed in require at C:\TigerCub\t\response/Xfer/_get_next_valid_candidate.pm line 11. BEGIN failed--compilation aborted at C:\TigerCub\t\response/Xfer/_get_next_valid_candidate.pm line 11. Compilation failed in require at (eval 6) line 3. Commenting out lines 669 and 1696 make it work fine. I remember having this discussion a few months back but did not find a solution. Apparently it is still an issue. William -- Knowmad Services Inc. http://www.knowmad.com
