Automated smoke report for 5.27.9 patch 
e7206367046d4f58fd12d34816a357cc5535a02f v5.27.8-321-ge720636704
scaleway:  ( 0MHz) (aarch64/4 cpu)
    on        linux - 4.14.13-mainline-rev1 [debian]
    using      gcc-6 version 6.3.0 20170516
    smoketime 11 hours 13 minutes (average 1 hour 24 minutes)

Summary: FAIL(X)

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

v5.27.8-321-ge720636704  Configuration (common) -Acc=gcc-6
----------- ---------------------------------------------------------
O -         -Accflags="-O2" -Duseithreads
O -         -Accflags="-O2" -Duseithreads -Duse64bitint
X -         -Accflags="-O2" -Duseithreads -Duselongdouble
X -         -Accflags="-O2" -Duseithreads -Dusemorebits
O -         -Accflags="-O2 -Wall" -Duseithreads
O -         -Accflags="-O2 -Wall" -Duseithreads -Duse64bitint
X -         -Accflags="-O2 -Wall" -Duseithreads -Duselongdouble
? -         -Accflags="-O2 -Wall" -Duseithreads -Dusemorebits
| +--------- -DDEBUGGING
+----------- no debugging

Locally applied patches:

Failures: (common-args) -Acc=gcc-6
[default] -Accflags="-O2" -Duseithreads -Duselongdouble
[default] -Accflags="-O2" -Duseithreads -Dusemorebits
[default] -Accflags="-O2 -Wall" -Duseithreads -Duselongdouble
Inconsistent test results (between TEST and harness):
.................................................. FAILED at test 53

Compiler messages(gcc):
regcomp.c: In function ‘S_reg’:
embed.h:979:32: warning: ‘ret’ may be used uninitialized in this function 
ODBM_File.c: In function ‘XS_ODBM_File_DELETE’:
ODBM_File.xs:64:31: warning: identifier ‘delete’ conflicts with C++ keyword 
re_comp.c: In function ‘S_reg’:
../../embed.h:979:32: warning: ‘ret’ may be used uninitialized in this function 

Report by Test::Smoke v1.53 build 1374 running on perl 5.24.1
(Reporter v0.050 / Smoker v0.045)

Reply via email to