Smoke logs available at 
http://m-l.org/~perl/smoke/perl/linux/blead_g++_quick/loge09e3cee34fbe40a471dc2fa31f2b8533598fb45.log.gz

Automated smoke report for 5.21.4 patch 
e09e3cee34fbe40a471dc2fa31f2b8533598fb45 v5.21.3-171-ge09e3ce
zwei: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (GenuineIntel 2668MHz) (x86_64/8 
cpu)
    on        linux - 3.13.0-33-generic [debian]
    using     g++ version 4.8.2
    smoketime 1 hour 16 minutes (average 19 minutes)

Summary: PASS

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.3-171-ge09e3ce  Configuration (common) -Accflags=-DPERL_POISON -Dcc=g++
----------- ---------------------------------------------------------
O O         
O O         -Duseithreads
| +--------- -DDEBUGGING
+----------- no debugging


Locally applied patches:
    SMOKEe09e3cee34fbe40a471dc2fa31f2b8533598fb45

Testsuite was run only with 'harness'

Compiler messages(gcc):
MD5.xs: In function ‘void XS_Digest__MD5_md5(CV*)’:
../../handy.h:455:36: warning: null argument where non-null required (argument 
1) [-Wnonnull]
POSIX.o: In function `XS_POSIX_tmpnam(cv*)':
POSIX.o: In function `XS_POSIX_tmpnam':
/home/perl/smoke/perl/blead_g++_quick/build/ext/POSIX/POSIX.xs:1520: warning: 
the use of `tmpnam' is dangerous, better use `mkstemp'
vutil.c:36:1: warning: unused parameter ‘my_perl’ [-Wunused-parameter]
MD5.xs: In function ‘void XS_Digest__MD5_md5(PerlInterpreter*, CV*)’:
POSIX.o: In function `XS_POSIX_tmpnam(interpreter*, cv*)':
threads.xs: In function ‘ithread* S_ithread_create(PerlInterpreter*, SV*, IV, 
int, int, int, int)’:
threads.xs:721:60: warning: ignoring return value of ‘ssize_t write(int, const 
void*, size_t)’, declared with attribute warn_unused_result [-Wunused-result]
-- 
Report by Test::Smoke v1.53 build 1374 running on perl 5.18.2
(Reporter v0.050 / Smoker v0.045)

Reply via email to