Automated smoke report for 5.19.4 patch 
c6e3faeac94bbf64e9e6f70354d0c88b9de450e3 v5.19.3-77-gc6e3fae
deimos.tony.develop-help.com: AMD 686-class (amd64/2 cpu)
    on        netbsd - 5.1.2
    using     cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120)
    smoketime 4 hours 45 minutes (average 23 minutes 49 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.19.3-77-gc6e3fae  Configuration (common) none
----------- ---------------------------------------------------------
O O O O     
F O O O     -Duse64bitint
O O O O     -Dmad
O O O O     -Duseithreads
F O O O     -Duseithreads -Duse64bitint
O O O O     -Duseithreads -Dmad
| | | +----- PERLIO = perlio -DDEBUGGING
| | +------- PERLIO = stdio  -DDEBUGGING
| +--------- PERLIO = perlio
+----------- PERLIO = stdio


Locally applied patches:
    SMOKEc6e3faeac94bbf64e9e6f70354d0c88b9de450e3

Testsuite was run only with 'harness' and HARNESS_OPTIONS=j4

Failures: (common-args) none
[stdio] -Duse64bitint
../lib/Benchmark.t..........................................FAILED
    127-128
    Non-zero exit status: 2

[stdio] -Duseithreads -Duse64bitint
../lib/Benchmark.t..........................................FAILED
    66
    Non-zero exit status: 1

Passed Todo tests: (common-args) none
[stdio/perlio] -Duseithreads
[stdio/perlio] -DDEBUGGING -Duseithreads
[stdio/perlio] -Duseithreads -Duse64bitint
[stdio/perlio] -DDEBUGGING -Duseithreads -Duse64bitint
[stdio/perlio] -Duseithreads -Dmad
[stdio/perlio] -DDEBUGGING -Duseithreads -Dmad
../cpan/List-Util/t/readonly.t..............................PASSED
    10
UUID: 0C1746D4-0C71-11E3-B381-9FCA11A1F292
Branch: blead
Config: default
Logs: http://perl.develop-help.com/reports/

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

Reply via email to