Geoffrey Young wrote:

>>The ReallyFirst test runs OK on its own, though.
>>    
>>
>
>it seems I forgot to add a -DReallyFirst, so this is running the default as
>well.
>
Doh!  Have you added it now?  I've built & installed this new patch and 
I still find that -DReallyFirst works fine...

>
>  
>
>>    
>>
>>>finally, is there something screwy with my IO in t/TEST - if you take out
>>>all the open and print foo does the problem go away?  that was mostly for my
>>>debugging information anyway...
>>>
>>>      
>>>
>>Removing all the open/print/close stuff makes no difference.
>>    
>>
>
>ok.  I don't suppose that sleeping between startups makes a difference?
>
Sleeping between what?  One test /on its own/ doesn't work!

In fact, even this produces the usual error in the log and crashes the 
server:

C:\Temp\hook_order_test-mp2>C:/apache2/bin/Apache.exe -d 
C:/Temp/hook_order_test-mp2/t -f 
C:/Temp/hook_order_test-mp2/t/conf/httpd.conf -D APACHE2 -D 
PERL_USEITHREADS -D ReallyLast -X

(That's what I was running through the debugger.  I meant to say.)

>[...]
>  
>
>I spent the entire morning trolling through the winnt mpm and win32 API
>documentation and I'm stumped - I can't see the interaction between this
>code and what I'm doing at all.  furthermore, the two events are created far
>_after_ I am finished doing stuff, since ap_run_mpm is called after
>post-config, so it's not like I am erasing a previously initialized state.
>
>anyway, attached is yet another patch.  the main difference here is in the
>pools, so maybe that will have a positive effect :)  
>
Sadly not.  I still get the same failure as before.

>stas at one point
>suggested nulling the table when I'm done with it, which might also be an
>idea - IIRC, there is some config-parsing done on shutdown as well, so maybe
>something is getting stuck using the table created with a dead pool or
>something.
>
[I'll try your other (off-list) patch in a moment]

>
>the only thing I could suggest at this point is to comment out the
>apr_hook_sort_all() call in modperl_apache_resort_hooks() to see if there
>isn't something about that function (or calling it) that is mucking up the
>works.  what that would leave is the altering of the hook structure but (in
>theory) have no real effect since the hook order is the same as it was going in.
>
That makes a difference:  The original test suite now gets as far as the 
second test (-DReallyLast), which does this:

C:\apache2\bin\Apache.exe -d C:/Temp/hook_order_test-mp2/t -f 
C:/Temp/hook_order_test-mp2/t/conf/httpd.conf -D APACHE2 -D 
PERL_USEITHREADS -D ReallyLast
using Apache/2.0.48 (winnt MPM)

waiting 60 seconds for server to start: .
waiting 60 seconds for server to start: ok (waited 0 secs)
server localhost:8529 started
t\01first....skipped
        all skipped: no reason given
t\02last.....# Failed test 1 in t\02last.t at line 42
t\02last.....FAILED test 1
        Failed 1/1 tests, 0.00% okay
t\03mix......skipped
        all skipped: no reason given
Failed Test Stat Wstat Total Fail  Failed  List of Failed
-------------------------------------------------------------------------------
t\02last.t                 1    1 100.00%  1
2 tests skipped.

There's nothing interesting in the error_log, and the test suite is 
aborted there.  I assume the failure is simply because what's being 
tested for hasn't actually been done this time.

All the tests run OK (albeit with similar failures) in isolation.

>
>anyway, thanks so much for taking the time to play with this.  I hope it's
>fun at least :)
>
For the appropriate definition of "fun", yes ;)

- Steve



------------------------------------------------
Radan Computational Ltd.

The information contained in this message and any files transmitted with it are 
confidential and intended for the addressee(s) only.  If you have received this 
message in error or there are any problems, please notify the sender immediately.  The 
unauthorized use, disclosure, copying or alteration of this message is strictly 
forbidden.  Note that any views or opinions presented in this email are solely those 
of the author and do not necessarily represent those of Radan Computational Ltd.  The 
recipient(s) of this message should check it and any attached files for viruses: Radan 
Computational will accept no liability for any damage caused by any virus transmitted 
by this email.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to