On Wed, 16 May 2012, tony@develop-help.com wrote:
> Automated smoke report for 5.16.0 patch c43ca372962ed8b6058df231649647686874e1fe v5.16.0-RC2
> deimos.tony.develop-help.com: AMD 686-class (amd64/6 cpu)
> on netbsd - 5.1
> using cc version 4.1.3 20080704 prerelease (NetBSD nb2 20081120)
> smoketime 2 hours 7 minutes (average 10 minutes 38 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.16.0-RC2 Configuration (common) -Dstatic_ext=Socket
> ----------- ---------------------------------------------------------
> O O O O
> O O O F -Duse64bitint
> O O O O -Dmad
> F F O O -Duseithreads
> O O O O -Duseithreads -Duse64bitint
> F F O O -Duseithreads -Dmad
> | | | +----- PERLIO = perlio -DDEBUGGING
> | | +------- PERLIO = stdio -DDEBUGGING
> | +--------- PERLIO = perlio
> +----------- PERLIO = stdio
>
>
> Locally applied patches:
> RC2
> uncommitted-changes
> SMOKEc43ca372962ed8b6058df231649647686874e1fe
>
> Testsuite was run only with 'harness' and HARNESS_OPTIONS=j4
>
> Failures: (common-args) -Dstatic_ext=Socket
> [perlio] -DDEBUGGING -Duse64bitint
> [stdio/perlio] -Duseithreads
> ../lib/Benchmark.t..........................................FAILED
> 129
> Non-zero exit status: 1
I have been unable to reproduce this failures on NetBSD 5.1 (x86 single
core cpu) configured with -Duseithreads. I am unable to test the amd64
architecture. This test doesn't fail for me, but does take an unusually
long time -- over 28 minutes (compared to 27 seconds on Solaris 11 on
similar hardware). There's something wrong there, but I don't know
what yet.
> [perlio] -Duseithreads -Dmad
> ../cpan/Memoize/t/tie_sdbm.t................................FAILED
> Non-zero exit status: 1
> No plan found in TAP output
> ../lib/DBM_Filter/t/02core.t................................FAILED
> Non-zero exit status: 1
> Bad plan. You planned 189 tests but ran 4.
> ../lib/DBM_Filter/t/compress.t..............................FAILED
> Non-zero exit status: 1
> Bad plan. You planned 23 tests but ran 8.
> ../lib/DBM_Filter/t/encode.t................................FAILED
> Non-zero exit status: 1
> Bad plan. You planned 26 tests but ran 10.
> ../lib/DBM_Filter/t/int32.t.................................FAILED
> Non-zero exit status: 1
> Bad plan. You planned 22 tests but ran 7.
> ../lib/DBM_Filter/t/null.t..................................FAILED
> Non-zero exit status: 1
> Bad plan. You planned 26 tests but ran 7.
> ../lib/DBM_Filter/t/utf8.t..................................FAILED
> Non-zero exit status: 1
> Bad plan. You planned 20 tests but ran 9.
> ../ext/SDBM_File/t/sdbm.t...................................FAILED
> Non-zero exit status: 1
> No plan found in TAP output
I haven't been able to reproduce these on NetBSD-5.1 on x86.
--
Andy Dougherty doughera@lafayette.edu
Thread Next