I don't understand why so few combinations are being run:
On Mon, Sep 22, 2003 at 11:38:14AM +0100, Nicholas Clark wrote:
> Automated smoke report for 5.8.1 patch 21308 on freebsd - 4.8-rc (i386/1 cpu)
> (colon.colondot.net) using ccache gcc version 2.95.4 20020320 [FreeBSD]
> Report by Test::Smoke v1.18.02 (perl 5.00503) [1 hour 50 minutes]
>
> O = OK F = Failure(s), extended report at the bottom
> X = test(s) failed 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
>
> 21308 Configuration (common) -DPERL_COPY_ON_WRITE -Dcc='ccache gcc'
> ------------ ----------------------------------------------------------------
> ? ? O O -Duseperlio -Dusethreads -Duseithreads -Dusereentrant
> (cont) -Dusemymalloc=n -Dusedl=n
> ? ? O O -Duseperlio -Dusethreads -Duseithreads -Dusereentrant
> (cont) -Dusemymalloc=y -Dusedl=n
> ? ? O O -Duseperlio -Dusethreads -Duseithreads -Dusereentrant
> (cont) -Duse64bitint -Dusemymalloc=n -Dusedl=n
> ? ? O X -Duseperlio -Dusethreads -Duseithreads -Dusereentrant
> (cont) -Duse64bitint -Dusemymalloc=y -Dusedl=n
> | | | +----- PERLIO = perlio -DDEBUGGING
> | | +------- PERLIO = stdio -DDEBUGGING
> | +--------- PERLIO = perlio
> +----------- PERLIO = stdio
>
> Summary: PASS-so-far
>
>
> Failures:
>
> freebsd [perlio ]-DDEBUGGING -Duseperlio -Dcc='ccache gcc'
> (cont) -Dusethreads -Duseithreads -Dusereentrant
> (cont) -Duse64bitint -Dusemymalloc=y -Dusedl=n
> (cont) -DPERL_COPY_ON_WRITE
> Inconsistent testresults:
> lib/Memoize/t/expmod_t...............FAILED at test 15
>
I've attached the config. The log ends:
PERLIO = stdio All tests successful.
u=7.59 s=3.35 cu=463.06 cs=54.92 scripts=791 tests=77418
OK, archive results ...
PERLIO = perlio lib/Memoize/t/expmod_t...............FAILED at test 15
Failed 1 test script out of 791, 99.87% okay.
### Since not all tests were successful, you may want to run some of
### them individually and examine any diagnostic messages they produce.
### See the INSTALL document's section on "make test".
### You have a good chance to get more information by running
### ./perl harness
### in the 't' directory since most (>=80%) of the tests succeeded.
u=7.59 s=3.68 cu=447.66 cs=56.97 scripts=791 tests=77418
*** Error code 1
Stop in /export/home/nwc10/Smoke/Maint-Even.
*** Error code 1
Stop in /export/home/nwc10/Smoke/Maint-Even.
Error while reading test-results: 1 at /export/home/nwc10/Smoke/smoke/Test/Smoke
.pm line 141
Extending failures with Harness
Inconsistent testresults:
lib/Memoize/t/expmod_t...............FAILED at test 15
*** Error code 1
Stop in /export/home/nwc10/Smoke/Maint-Even.
*** Error code 1
Stop in /export/home/nwc10/Smoke/Maint-Even.
Finished smoking 21308
Sending report to [EMAIL PROTECTED] OK
I got the same early termination on a previous run (21300), and Memoize
didn't fail a test there, so the inconsistent result isn't the problem.
I'm confused
Nicholas Clark#-Uuseperlio -Dcc='ccache gcc'
-Duseperlio -Dcc='ccache gcc'
=
-Dusethreads -Duseithreads -Dusereentrant
=
-Duse64bitint
=
-Dusemymalloc=n
-Dusemymalloc=y
=
-Dusedl=n
=
/-DDEBUGGING/
-DDEBUGGING
=
#/-DDEBUGGING/
#
#-DCAST_INLINE
=
/-DDEBUGGING/
#-DNO_PERL_PRESERVE_IVUV
-DPERL_COPY_ON_WRITE
#-DCRIPPLED_CC
