Jerry D. Hedden wrote:
> Steve Hay wrote:
>> Automated smoke report for 5.11.0 patch 33390
>> maldoror.bath.planit.group: Intel(R) Core(TM)2 CPU 6700 @
>> 2.66GHz(~2659 MHz) (x86/2 cpu) on MSWin32 - WinXP/.Net SP2
>> using cl version 13.10.3077
>> smoketime 5 hours 7 minutes (average 15 minutes 23 seconds)
>>
>> Summary: FAIL(F)
>>
>> Failures: (common-args) -DCCTYPE=MSVC70FREE
>> -DINST_TOP=$(INST_DRV)\Smoke\doesntexist [default] -DDEBUGGING
>> -Duseithreads
>> ../ext/IO/t/io_multihomed.t.................................FAILED
>> ../ext/threads/shared/t/stress.t............................FAILED
>
> When stress.t fails, it outputs diagnostics.
> Any chance of getting those?
Hmm. It seems that stress.t didn't fail. It actually passed a TODO test,
and Test-Smoke has presuambly got confused over the output and logged it
as a failure:
Test Summary Report
-------------------
../ext/IO/t/io_multihomed.t (Wstat: 0
Tests: 6 Failed: 0)
Parse errors: Tests out of sequence. Found (8) but expected (6)
Bad plan. You planned 8 tests but ran 6.
../ext/threads/shared/t/stress.t (Wstat: 0
Tests: 1 Failed: 0)
TODO passed: 1
Files=1514, Tests=205458, 888 wallclock secs (34.95 usr + 2.34 sys =
37.30 CPU)
Result: FAIL
Failed 1/1514 test programs. 0/205458 subtests failed.
NMAKE : fatal error U1077: '..\perl.exe' : return code '0xff'
Stop.
error while running harness target 'test': 2 at
C:\Smokes\VC7F\ts/Test/Smoke.pm line 182
../ext/IO/t/io_multihomed.t.................................FAILED
Tests out of sequence. Found (8) but expected (6)
../ext/threads/shared/t/stress.t............................FAILED
