Re: Testsuite status/proper configure?

[Andreas Jaeger <aj at suse dot de>]

Michael Elizabeth Chastain <chastain@cygnus.com> writes:

> Your test process looks okay to me.
> 
> These are similar to my test results.  I run the test suite each weekend
> week and post the results to:
> 
>   http://sources.redhat.com/ml/gdb-testers

Thanks.  Now I have confidence to my results and will post them in the
proper way (with all needed info) next time.  The number of FAILS
suprised me.

> Nitpick #1: dejagnu does not report the count of ERRORs and WARNINGs.
> I have to count these by hand:
> 
>   grep -c ERROR gdb.sum
>   grep -c WARNING gdb.sum
> The triple "# ERRORs, # WARNINGs, # FAILs" is more useful than "# FAILs",
> because if something goes wrong, the results can have a lot of ERRORs
> and WARNINGs with fewer FAILs.

I'll add these next time.

> Nitpick #2: it helps to know which compiler you ran the test suite with.
> gdb should behave the same no matter what compiler that it's built
> with.  But the debug info in the programs-under-test depends a lot on
> what compiler it's built with and the version of that compiler.  In
> particular, there's a big difference between v2 gcc and v3 gcc.
> (I use a v3 gcc when I test).

I've used gcc 2.95.3.

> Basically your test process is good and those numbers are real.

Thanks for the confirmation,
Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj