Op een mooie zomerdag (Saturday 23 July 2005 17:29),schreef  Abe Timmerman:
> Automated smoke report for 5.9.3 patch 25214
> wodan: Intel Pentium II (Deschutes) (686-class) (i386/1 cpu)
>     on        netbsd - 1.5
>     using     /usr/pkg/gcc-2.95.3/bin/cc version 2.95.3 20010315 (release)
> (NetBSD nb1) smoketime 22 hours 1 minute (average 1 hour 22 minutes)
>
> Summary: FAIL(F)
...
> Failures: (common-args) -Dcc='/usr/pkg/gcc-2.95.3/bin/cc' -Ui_db
> [stdio/perlio]
> [stdio/perlio] -DDEBUGGING
> [stdio/perlio] -Duse64bitint
> [stdio/perlio] -DDEBUGGING -Duse64bitint
> [stdio/perlio] -Duseithreads
> [stdio/perlio] -DDEBUGGING -Duseithreads
> [stdio/perlio] -Duseithreads -Duse64bitint
> [stdio/perlio] -DDEBUGGING -Duseithreads -Duse64bitint
> [stdio/perlio] -DPERL_COPY_ON_WRITE
> [stdio/perlio] -DDEBUGGING -DPERL_COPY_ON_WRITE
> [stdio/perlio] -DPERL_COPY_ON_WRITE -Duse64bitint
> [stdio/perlio] -DDEBUGGING -DPERL_COPY_ON_WRITE -Duse64bitint
> [stdio/perlio] -DPERL_COPY_ON_WRITE -Duseithreads
> [stdio/perlio] -DDEBUGGING -DPERL_COPY_ON_WRITE -Duseithreads
> [stdio/perlio] -DPERL_COPY_ON_WRITE -Duseithreads -Duse64bitint
> [stdio/perlio] -DDEBUGGING -DPERL_COPY_ON_WRITE -Duseithreads -Duse64bitint
>     ../lib/version.t........................FAILED 79 173

Extending failures with harness:
        ../lib/version.t ../t/io/dup.t ../t/io/open.t

#     Failed test (../lib/version.t at line 239)
#          got: '1.00_415543946100'
#     expected: '1.23_0100'

#     Failed test (../lib/version.t at line 239)
#          got: '1.00_415543946100'
#     expected: '1.23_0100'
# Looks like you failed 2 tests of 183.


HTH +
Good luck,

Abe
-- 
Well, dereferencing that (as CvGV() would do) leads nowhere.  Or, as
the Ten Commandments for C Programmers quoth, "Thou shalt not follow
the NULL pointer, for chaos and madness await thee at its end."
                                   -- Jarkko Hietaniemi on p5p @ 2002-05-14

Reply via email to