Re: Smoke [5.6.1] 21024 FAIL(Fc) hp-ux b.11.00 (9000/800/2 cpus)

[ Most of the Dutch is (loosly) translated ]
Op een zonnige zomerdag (Friday 05 September 2003 12:28), schreef H.Merijn 
Brand:

> On Fri 05 Sep 2003 10:43, Campo Weijerman <[email protected]> wrote:
> > [email protected] (H.Merijn Brand) writes:
> > > On Fri 05 Sep 2003 01:09, Abe Timmerman <[email protected]> wrote:
> > > > Hoi Merijn,
> > > >
> > > > > Automated smoke report for 5.6.1 patch 21024 on hp-ux - b.11.00
> > > > > (9000/800/2 cpus) (a5) using  version
> > >
> > >                      ^        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > ??
> > >
> > > Kun je de versie van cc niet vinden?
> >
> > Volgens mij komt dit omdat deze header wordt opgebouwd met het
> > resultaat van de allerlaatste build in je smoke matrix.  Als die mis
> > gaat, zoals hier (zie onder) krijg je bogus data in de header.
> > Tenminste, zo was mijn ervaring met Test::Smoke <= 1.17

<translation density="high">
C-compiler info is only retrieved from the last build. No successfull 
Configure means no c-compiler info.
</translation>

Yup, that has always been a problem. I've been thinking about this, but 
haven't thought up a way to do this without breaking the current "mktest.out" 
format, so that'll have to go in 1.19 (which will replace mkovz.pl).

> Hah, en het was niet eens de bedoeling om dit op de reports te posten :)

I don't mind discussing these issues on <[email protected]>, they should be.

> Heb je suggesties voor een betere benadering? En hoe zou je omgaan met

<translation>Any suggestions?</translation>

> ==
>
> -Dcc=gcc
> ==

My personal view on this is: "Create a separate smoke config for each 
c-compiler and send multiple (smaller) reports from the same box.". I think 
that will reveal more detailed information about failures and the environment 
in which they occur.

The smoke_db has a decent interface to give you the information you may want 
for specific platforms or even cross platform/specific compiler version. That 
is why it is there (thanks Alain)!
I now think of the smoke-reports in terms of input for smoke_db (whilst still 
human readable).

> Automated smoke report for 5.6.1 patch 21024 on hp-ux - b.11.00 (9000/800/2
> cpus) (a5) using cc version B.11.11.25985.GP
>            gcc version 3.3
>            gcc64 version 3.3
> Report by Test::Smoke v1.18.05 (perl 5.8.0) [5 hours 33 minutes]

Although that looks nice, it needs more work as I want the failures (and 
successes!) linked with the compiler. It needs an extra reference to/from the 
configuration. Introducing that, will also need more complex parsing for 
smoke_db.

Here is the smoke_db:

	http://cpanplus.keradel.com/cgi-bin/smoke_db.cgi



Good luck,

Abe
-- 
Documenting bugs before they're found is kinda hard. 
Can I borrow your time machine? Mine won't start.
                                  -- Michael G. Schwern on p5p @ 2002-11-19