This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [testsuite] Increase gcc.dg/pr43058.c timeout

From: Mark Mitchell <mark at codesourcery dot com>
To: Mike Stump <mikestump at comcast dot net>
Cc: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>, gcc-patches at gcc dot gnu dot org
Date: Fri, 23 Jul 2010 11:05:50 -0700
Subject: Re: [testsuite] Increase gcc.dg/pr43058.c timeout
References: <yddr5j6ysjb.fsf@manam.CeBiTec.Uni-Bielefeld.DE> <81DC2B4B-E477-424C-B62D-20EE5EBB00C7@comcast.net>

Mike Stump wrote:

> Philosophy, any testcase that takes more than 30 seconds on a slow
> machine, is in danger of being a bad testcase. 

I tend to agree.  I'm not willing to make it a hard limit, because there
really are bugs that take a lot of processing to reproduce, and they may
be appropriate.

But, it's bothered me for about a decade that we spend X% of our test
cycles running Y% of our tests, where X >> Y.  The marginal costs of
slow tests is usually not commensurate with their marginal benefits.

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

Follow-Ups:
- Re: [testsuite] Increase gcc.dg/pr43058.c timeout
  - From: Rainer Orth

References:
- [testsuite] Increase gcc.dg/pr43058.c timeout
  - From: Rainer Orth
- Re: [testsuite] Increase gcc.dg/pr43058.c timeout
  - From: Mike Stump

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]