source mgt. requirements solicitation

[Craig Rodrigues]

On Sun, Dec 08, 2002 at 04:22:22PM -0800, Tom Lord wrote:
> One quick request: someone said "Hey, testing is already automated."
> Can I please see a slight elaboration on the form and function of that
> automation?  

As far as I can tell, there are are number of people who run
daily (or frequent) builds of GCC on a few platforms.  They
use the output of "make test", which kicks off some tests which
use the DejaGNU testing framework, and post their output
to the gcc-testresults mailing list:

http://gcc.gnu.org/ml/gcc-testresults/

CodeSourcery has been working on converting the GCC testsutie
over to QMTest:
http://gcc.gnu.org/ml/gcc/2002-05/msg01978.html

While the existing GCC testing process has its benefits, I don't
think it is perfect.  It would be great if someone had some 
positive ideas towards improving the GCC testing process.

To give you some ideas of some of the problems in the current
process, Wolfgang Banerth has informed me that he has
identified 71 current C++ regressions from GCC 3.2 in the mainline 
branch of GCC, based on reading reports in GNATS.
Granted, many of these regressions might be related and duplicates, but
still, that is quite a number of regressions to track down and fix.
I'd be very interested in any ideas which could improve this process.

-- 
Craig Rodrigues        
http://www.gis.net/~craigr    
rodrigc@attbi.com