On Sat, Sep 08, 2001 at 01:33:01AM -0700, Thaddeus Pritchard wrote:
> linux stdio/perlio -Dusemymalloc -Uuseperlio
<snip>
> linux stdio/perlio -DDEBUGGING -Dusemymalloc -Duseperlio=stdio
>-Duse64bitall -Duselongdouble
> ext/DB_File/t/db-recno.............FAILED at test 61
That's troublesome. Could you reconfig in one of those configs, rerun
that test and show the whole output?
> linux perlio -Dusemymalloc -Dusethreads -Duseithreads
> lib/Memoize/t/speed................FAILED at test 2
I'm concerned that this test might just be a false failure because
someone decided to bzip a file when it ran or something. Could you
rerun that test with that config?
> linux stdio -DDEBUGGING -Dusemymalloc -Dusethreads -Duseithreads
>-Dusemultiplicity -Uuseperlio -Duse64bitint
> op/rand............................FAILED at test 4
This one is probably just a false "1 in 100" failure from running it
some many times. You *just* missed the patch (11837) that made that 1
in 100 into more like 1 in 1000.
> linux stdio -DDEBUGGING -Dusemymalloc -Dusethreads -Duseithreads
>-Dusemultiplicity -Dusereentrant -Uuseperlio
> ext/Time/HiRes/HiRes...............FAILED at test 11
>
> linux stdio -DDEBUGGING -Dusemymalloc -Dusethreads -Duseithreads
>-Dusemultiplicity -Dusereentrant -Duseperlio
> ext/Time/HiRes/HiRes...............FAILED at test 8
>
> linux perlio -DDEBUGGING -Dusemymalloc -Dusethreads -Duseithreads
>-Dusemultiplicity -Dusereentrant -Duseperlio
> ext/Time/HiRes/HiRes...............FAILED at test 11
Reconfig and run one of these, too, please.
--
Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
Maybe they hooked you up with one of those ass-making magazines.
-- brian d. foy as misheard by Michael G Schwern
