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: dejagnu: timeout?


On 8/21/06, Christian Joensson <christian.joensson@gmail.com> wrote:
I just noticed a slight change in behaviour... on my system, I have
edited dejagnu's remote.exp such that it defaults its timeout to 1800
instead of 300. However, on gcc trunk, I see that, for example, in the
libstdc++ testsuite log, the timeout is set to 600, while in, e.g.,
gcc's log file, its 1800, as I expect.

Now, is there some change that  has been made to gcc trunk lately,
meaning the last year, that have this effect?

sorry, too early, it's http://gcc.gnu.org/ml/gcc-cvs/2006-06/msg00792.html ...


Any suggestions on how I could get gcc trunk testsuite to once again
use dejagnu timeout to 1800?

so, basically, how would I override http://gcc.gnu.org/ml/gcc-cvs/2006-06/msg00792.html , without having a local change in my source tree, such that I get my old behaviour?

--
Cheers,

/ChJ


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