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

Smoke [blead] v5.21.4-43-gc354df0 FAIL(F) linux 3.13.0-36-generic [debian] (x86_64/8 cpu) {blead_clang_quick}

George Greer
September 22, 2014 17:08
Smoke [blead] v5.21.4-43-gc354df0 FAIL(F) linux 3.13.0-36-generic [debian] (x86_64/8 cpu) {blead_clang_quick}
Message ID:
Smoke logs available at

Automated smoke report for 5.21.5 patch c354df01f41f08af4a9abac9e1869124c5691916 v5.21.4-43-gc354df0
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     clang version 4.2.1 Compatible Ubuntu Clang 3.4 (tags/RELEASE_34/final)
    smoketime 1 hour 20 minutes (average 20 minutes 14 seconds)

Summary: FAIL(F)

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.4-43-gc354df0  Configuration (common) -Accflags="-DPERL_POISON -Werror=declaration-after-statement" -Dcc=clang
----------- ---------------------------------------------------------
O F         
O O         -Duseithreads
| +--------- -DDEBUGGING
+----------- no debugging

Locally applied patches:

Testsuite was run only with 'harness'

Failures: (common-args) -Accflags="-DPERL_POISON -Werror=declaration-after-statement" -Dcc=clang
[default] -DDEBUGGING
    Non-zero exit status: 115
    No plan found in TAP output

Compiler messages(gcc):
POSIX.o: In function `XS_POSIX_tmpnam':
/home/perl/smoke/perl/blead_clang_quick/build/ext/POSIX/POSIX.xs:2725: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
Pattern(gcc): /(^(?-s:.+?):(?: In function .+?:$|(?: undefined reference to .+?$)|\d+(?:\:\d+)?: (?:warning:|error:|invalid) .+?$))/
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