Re: [testsuite, ada] Convert ACATS to DejaGnu (PR testsuite/37703)

[Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>]

"Joseph S. Myers" <joseph@codesourcery.com> writes:

> For the general issue: a slow test appears to have served its purpose by 
> showing up a (target-specific) bug in the compiler.  And in general you 
> need to consider whether a resource-hungry test is actually showing up a 
> bug and should not be so resource-hungry, before reducing the test size or 

Right: I had such a case recently where one testcase was slower by a
factor of 3 on one particular x86 CPU:

	http://gcc.gnu.org/ml/gcc-patches/2011-01/msg01234.html

I'll probably revisit this one with the Studio profiling tools.

> only running it conditionally.  (You might still reduce it after finding 
> it shows a bug - but only after filing that bug in Bugzilla; not simply 
> blindly presume that the test is too big for the testsuite.)

Sure.  While this takes some effort, it can have considerable benefits
as this case has shown.  On the other hand, spending literally 45
minutes in a single fortran testcase run as a torture test when that
isn't necessary seems to server no one.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University