Stas Bekman wrote:

>Let's try another time to resolve that t/perl/ithreads.t. My problem is 
>reproducing the failure. I certainly know that it exists, but it's always 
>random and never on its own. And it's been awhile since I last got it.
>
>What happens on win32? does it always fail? does it fail on its own? if so 
>could you try to shrink the test to the minimal possible code, while it's 
>still failing?
>  
>
The mail I sent on 14 Sep 2004 still holds true for me:

http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=109515364713173&w=2

i.e. this sequence of tests fails (every time):

perl t/TEST -verbose t/modules/reload.t t/perl/api.t t/perl/ithreads.t

but leaving any one of those tests out fixes the failure.  All three 
tests also work in isolation.

The failure manifests itself as a server crash -- Apache.exe exits 
causing t/perl/ithreads.t itself to fail with this "verbose" output:

t\perl\ithreads.....request has failed (the response code was: 500)
see t/logs/error_log for more details

but there is nothing written to the error_log.

>Next I want you to try cutting off things from startup files and 
>httpd.conf, to find whether it's some unrelated module that is loaded that 
>causes the problem. I suspect that because the sister test 
>t/perl/ithreads2.t doesn't fail, and it runs exactly the same code, but 
>inside a dedicated interpreter pool, which doesn't load any other modules.
>
Will try (again), but I've tried this before and got nowhere with it :(

- 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