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: GCC 4.2.1 : testsuite says WARNING: program timed out

From: "Christian Joensson" <christian dot joensson at gmail dot com>
To: "Rupert Wood" <me at rupey dot net>
Cc: "Dennis Clarke" <dclarke at blastwave dot org>, "David Daney" <ddaney at avtrex dot com>, gcc at gcc dot gnu dot org
Date: Wed, 1 Aug 2007 14:42:33 +0200
Subject: Re: GCC 4.2.1 : testsuite says WARNING: program timed out
References: <46895.72.39.216.186.1185955039.squirrel@mail.blastwave.org> <46B03FAF.3040906@avtrex.com> <46928.72.39.216.186.1185956058.squirrel@mail.blastwave.org> <041701c7d419$68818ca0$3984a5e0$@net>

2007/8/1, Rupert Wood <me@rupey.net>:
> Dennis Clarke wrote:
>
> >    Is there a way to allow the testsuite to just run regardless of
> >    how long it takes?
>
> I think you need to pass "set timeout -1" into dejagnu. I'd suggest a larger positive timeout instead.
>
> I forget the correct way to do this - I used to end up editing the .exp files in /usr/share/dejagnu.

that's right, however, I recall some issues with, e.g., libstdc++
testsuite not using the system set in, if memory serves me right,
remote.exp.

-- 
Cheers,

/ChJ

References:
- GCC 4.2.1 : testsuite says WARNING: program timed out
  - From: Dennis Clarke
- Re: GCC 4.2.1 : testsuite says WARNING: program timed out
  - From: David Daney
- Re: GCC 4.2.1 : testsuite says WARNING: program timed out
  - From: Dennis Clarke
- RE: GCC 4.2.1 : testsuite says WARNING: program timed out
  - From: Rupert Wood

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