[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [DejaGnu] Enhancement: Provide a mechanism to override the lame 300

From: John David Anglin
Subject: Re: [DejaGnu] Enhancement: Provide a mechanism to override the lame 300 second timeout default
Date: Fri, 18 May 2001 11:41:20 -0400 (EDT)

> On Thu, May 17, 2001 at 04:45:03PM -0400, John David Anglin wrote:
> > In remote.exp, the default timeout is set to 300 seconds.  It would
> > be nice if there was a default timeout variable that could be set to
> > a different value in site.exp or whatever.  That way I don't have to
> > edit remote.exp to change the default for slow machines whenever I
>   When this was considered before, nobody was sure of whether there
> should be a default timeout value (which could be set in site.exp), or
> whether it should be a mulitplier, that applies to the current timeout
> value. Many of the GDB tests have varying timeouts, and the idea was that
> sometimes you *want* a timeout.  I'm undecided as to which behaviour would
> be best. Ideas anyone ?

How about both?  The multiplier could apply to both the default and
test-specified timeout.  The current code always uses the test-specified
value if provided.  Since sometimes you *want* a timeout, require the
multiplier to be >= 1 (ie., the user can only increase the default or
test-specified value, and can't disable the timeout with the multiplier).

J. David Anglin                                  address@hidden
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]