Nicholas Clark wrote:

>Hello to our friends at asconsultancy.com who clearly haven't got a clue when
>it comes to configuring autorepsonders.
>
>On Mon, Jun 20, 2005 at 07:30:00AM +0100, Steve Hay wrote:
>
>  
>
>>Failures: (common-args) -DINST_TOP=$(INST_DRV)\Smoke\doesntexist
>>[default] -Duseithreads
>>[default] -DDEBUGGING -Duseithreads
>>[default] -Duseithreads -Duselargefiles
>>[default] -DDEBUGGING -Duseithreads -Duselargefiles
>>[default] -Accflags='-DPERL_COPY_ON_WRITE' -Duseithreads
>>[default] -DDEBUGGING -Accflags='-DPERL_COPY_ON_WRITE' -Duseithreads
>>[default] -Accflags='-DPERL_COPY_ON_WRITE' -Duseithreads -Duselargefiles
>>[default] -DDEBUGGING -Accflags='-DPERL_COPY_ON_WRITE' -Duseithreads 
>>-Duselargefiles
>>    ../ext/threads/t/problems.t.............FAILED ??
>>    
>>
>
>I suspect that this may be me and it may be change 24896.
>  
>
I suspect not.  I think it is the same old intermittent failure that 
I've been having for a loooong time now, e.g. the smokes at patchlevels 
24856, 24828, 24798, ... all show the same errors.

The smoke log says

../ext/threads/t/problems...................dubious
    Test returned status 5 (wstat 1280, 0x500)
    after all the subtests completed successfully

and indeed whenever I've seen it when running the tests interactively it 
is always an access violation when exiting the script (after all tests OK).



------------------------------------------------
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.

Reply via email to