develooper Front page | perl.perl5.porters | Postings from October 2014

Smoke [blead] v5.21.5-96-ge1817ab FAIL(m) linux 3.13.0-36-generic [debian] (x86_64/8 cpu) {blead_g++_quick}

George Greer
October 25, 2014 20:14
Smoke [blead] v5.21.5-96-ge1817ab FAIL(m) linux 3.13.0-36-generic [debian] (x86_64/8 cpu) {blead_g++_quick}
Message ID:
Smoke logs available at

Automated smoke report for 5.21.6 patch e1817ab9e1b3103a20f0236757fcabee412a82f7 v5.21.5-96-ge1817ab
zwei: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (GenuineIntel 2668MHz) (x86_64/8 cpu)
    on        linux - 3.13.0-36-generic [debian]
    using     g++ version 4.8.2
    smoketime 15 minutes 52 seconds (average 3 minutes 58 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

v5.21.5-96-ge1817ab  Configuration (common) -Accflags=-DPERL_POISON -Dcc=g++
----------- ---------------------------------------------------------
m m         
m m         -Duseithreads
| +--------- -DDEBUGGING
+----------- no debugging

Locally applied patches:

Testsuite was run only with 'harness'

Compiler messages(gcc):
regcomp.c:16154:1: warning: unused parameter ‘pRExC_state’ [-Wunused-parameter]
op.c: In function ‘OP* Perl_op_lvalue_flags(OP*, I32, U32)’:
op.c:2640:9: error: ‘iv’ does not name a type
op.c:2643:35: error: ‘iv’ was not declared in this scope
sv.h:1233:4: error: expected primary-expression before ‘)’ token
sv.h:1233:4: error: expected ‘;’ before ‘)’ token
vutil.c:36:1: warning: unused parameter ‘my_perl’ [-Wunused-parameter]
regcomp.c:3716:1: warning: unused parameter ‘my_perl’ [-Wunused-parameter]
op.c: In function ‘OP* Perl_op_lvalue_flags(PerlInterpreter*, OP*, I32, U32)’:
Report by Test::Smoke v1.53 build 1374 running on perl 5.18.2
(Reporter v0.050 / Smoker v0.045) Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About