On Wed, 4 Jan 2006 21:05 -0700, [EMAIL PROTECTED] wrote:

> Automated smoke report for 5.9.3 patch 26654
> harpo.jimc.earth: Intel(R) Pentium(R) M processor 1.70GHz (GenuineIntel
> 1695MHz) (i686/1 cpu) on        linux - 2.6.14-1.1653_FC4 [fedora]
>     using     cc version 4.0.2 20051125 (Red Hat 4.0.2-8)
>     smoketime 4 hours 51 minutes (average 18 minutes 11 seconds)
> 
> Summary: FAIL(X)
> 
> 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

Wow! Does this also mean that our open discussion about longdoubles can be
considered closed?
"strange Configure problem affecting NV_ZERO_IS_ALLBITS_ZERO -> smoke
failures"

>    26654     Configuration (common) none
> ----------- ---------------------------------------------------------
> O O O O     
> O O O O     -Duse64bitint
> O O O O     -Duselongdouble
> O O O O     -Dusemorebits
> O O O O     -Duseithreads
> O O O O     -Duseithreads -Duse64bitint
> O O O O     -Duseithreads -Duselongdouble
> O O X O     -Duseithreads -Dusemorebits
> | | | +----- PERLIO = perlio -DDEBUGGING
> | | +------- PERLIO = stdio  -DDEBUGGING
> | +--------- PERLIO = perlio
> +----------- PERLIO = stdio
> 
> Locally applied patches:
>     DEVEL24148
>     unify PL_body_arenaroots[] 1.2 (../dev/diff.one-arenalist-1.2)
>     arena-sets-1 (../dev/diff.arenasets-1)
>     SMOKE26654
> 
> Failures: (common-args) none
> [stdio] -DDEBUGGING -Duseithreads -Dusemorebits
> Inconsistent test results (between TEST and harness):
>     ../lib/Benchmark.t......................FAILED at test 13

-- 
H.Merijn Brand        Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using Perl 5.6.2, 5.8.0, 5.8.5, & 5.9.2  on HP-UX 10.20, 11.00 & 11.11,
 AIX 4.3 & 5.2, SuSE 9.2 & 9.3, and Cygwin. http://www.cmve.net/~merijn
Smoking perl: http://www.test-smoke.org,    perl QA: http://qa.perl.org
 reports  to: [EMAIL PROTECTED],                [email protected]

Reply via email to