Automated smoke report for 5.9.5 patch 31613
maldoror.bath.planit.group: Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz(~2660 MHz) 
(x86/2 cpu)
    on        MSWin32 - WinXP/.Net SP2
    using     bcc32 version 5.5.1
    smoketime 9 minutes 43 seconds (average 29.150 seconds)

Summary: FAIL(M)

O = OK  F = Failure(s), extended report at the bottom
X = Failure(s) under TEST but not under harness
? = still running or test results not (yet) available
Build failures during:       - = unknown or N/A
c = Configure, m = make, M = make (after miniperl), t = make test-prep

   31613     Configuration (common) -DCCTYPE=BORLAND 
-DINST_TOP=$(INST_DRV)\Smoke\doesntexist
----------- ---------------------------------------------------------
M M         
M M         -Dusemymalloc
M M         -Duselargefiles
M M         -Duselargefiles -Dusemymalloc
M M         -Duseithreads -Uuseimpsys
M M         -Duseithreads -Uuseimpsys -Dusemymalloc
M M         -Duseithreads -Uuseimpsys -Duselargefiles
M M         -Duseithreads -Uuseimpsys -Duselargefiles -Dusemymalloc
M M         -Duseithreads
M M         -Duseithreads -Duselargefiles
| +--------- -DDEBUGGING
+----------- no debugging

Locally applied patches:
    DEVEL
    SMOKE31613

Compiler messages(bcc32):
Warning W8071 ..\generate_uudmap.c 17: Conversion may lose significant digits 
in function main
Warning W8013 ..\perly.c 270: Possible use of 'i' before definition in function 
S_clear_yystack
Warning W8013 ..\regcomp.c 4345: Possible use of 'copyRExC_state' before 
definition in function Perl_re_compile
Warning W8019 ..\regexec.c 4789: Code has no effect in function S_regmatch
Warning W8065 win32.c 1671: Call to function 'out_of_memory' with no prototype 
in function win32_ansipath
Warning W8065 win32.c 1680: Call to function 'out_of_memory' with no prototype 
in function win32_ansipath
Warning W8065 win32.c 1687: Call to function 'out_of_memory' with no prototype 
in function win32_ansipath

-- 
Report by Test::Smoke v1.19_86 build 1044 running on perl 5.9.5
(Reporter v0.027 / Smoker v0.032)

Reply via email to