This change: http://gcc.gnu.org/ml/gcc-patches/2006-06/msg01487.html
Has caused problems with people who set a custom timeout value in .exp files. Examples include: http://gcc.gnu.org/ml/gcc/2006-08/msg00371.html and http://gcc.gnu.org/ml/libstdc++/2006-08/msg00027.html Mike's suggestion to do timeout=timeout*2 is interesting, but I don't know if that really solves the issue. Perhaps the answer that I'm searching for is to see if timeout has been set, if so, use it. If not, set it. I'm hoping that some of the testsuite maintainers can figure out a better way to approach this whole issue. -benjamin -- Summary: configuring, over-riding timeout values in testsuite Product: gcc Version: 4.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: testsuite AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: bkoz at gcc dot gnu dot org GCC host triplet: all http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28870
