This is the mail archive of the gcc@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: fine grained control over testsuite

From: Ian Lance Taylor <iant at google dot com>
To: dclarke at blastwave dot org
Cc: gcc Maillist <gcc at gcc dot gnu dot org>
Date: Mon, 12 Mar 2012 13:47:57 -0700
Subject: Re: fine grained control over testsuite
References: <60722.10.0.66.17.1331487117.squirrel@interact.purplecow.org>

Dennis Clarke <dclarke@blastwave.org> writes:

> Q: is there a way to prevent a test timing out ?
>
> I see a lot of this sort of thing :
>
> Running /opt/bw/src/gcc-4.5.3/gcc/testsuite/gcc.c-torture/compile/compile.exp ...
> WARNING: program timed out.
> FAIL: gcc.c-torture/compile/pr46534.c  -O0  (test for excess errors)
> WARNING: program timed out.
> FAIL: gcc.c-torture/compile/pr46534.c  -O1  (test for excess errors)
> WARNING: program timed out.
> FAIL: gcc.c-torture/compile/pr46534.c  -O2  (test for excess errors)
> WARNING: program timed out.
> FAIL: gcc.c-torture/compile/pr46534.c  -O3 -fomit-frame-pointer  (test for
> excess errors)
> WARNING: program timed out.
> .
> .
> .
>
> Somewhat annoying as I am in no particular hurry.  :-)


You could get a faster computer.

Or you can edit gcc/site.exp in your build directory to set tool_timeout
to a large value.  The number is in seconds, and the default is 300.

Ian

References:
- fine grained control over testsuite
  - From: Dennis Clarke

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