Re: Smoke-testing configurations (was: More Ksh breakage on AIX 4.3.3 ML11)

Op een zonnige winterdag (Friday 07 March 2003 15:21), schreef H.Merijn Brand:

> On Fri 07 Mar 2003 12:17, Campo Weijerman <[email protected]> wrote:

[...]

> > >>>> Automated smoke report for 5.9.0 patch 18823 on aix - 3
> > >>>> (004068064c00/1 cpu) v1.16_21      using  version

I have never seen this on <[email protected]>, do you plan to send your 
reports there? (I hope so)

> > >>>> O = OK
> > >>>> F = Failure(s), extended report at the bottom
> > >>>> ? = still running or test results not (yet) available
> > >>>> Build failures during:       - = unknown
> > >>>> c = Configure, m = make, t = make test-prep
> > >>>>
> > >>>> 18823     Configuration (common) none
> > >>>> --------------------------------------------------------------------
> > >>>>-------- m m O -      -Uuseperlio
>
> Skip this one too. It's not supported anymore, but Abe still likes to test
> :P

Hmmm... could we have a pumpking verdict here... (about the support)

I really don't care what configurations are tested, but with Test::Smoke-1.17 
upcomming I would like to distribute a build-configurations default-file that 
tests those configurations the porters are interested in, but also gives them 
the ability to see that the "normal" stuff keeps working.

It depends on how you define "smoke-testing", I guess...

Perhaps we need to ponder on "standard" build-configurations vs 
"bleeding-edge" build-configurations (like -DPERL_COPY_ON_WRITE)


Good luck,

Abe
-- 
Anton Tagunov> P.S. People do like gory details :)

I don't like telling them.
                                   -- Jarkko Hietaniemi on p5p @ 2002-03-06