This is the mail archive of the 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

Mark Mitchell <> writes:

> 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.

Fully agreed.  The worst offender so far is a single gcc.c-torture
testcase that takes 4+ hours (2 multilibs, 8 different optimization
options) on an UltraSPARC-T2:

If this isn't changed, this single testcase runs longer than the rest of
the testsuite combined ;-(


Rainer Orth, Center for Biotechnology, Bielefeld University

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