[Bug testsuite/28870] [4.2 Regression] configuring, over-riding timeout values in testsuite

2006-10-09 Thread bkoz at gcc dot gnu dot org
--- Comment #8 from bkoz at gcc dot gnu dot org 2006-10-09 21:45 --- Note this issue is not c++ or libstdc++ specific. I see timeouts on old hardware all over the testsuite on gcc-testresults. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28870

[Bug testsuite/28870] [4.2 Regression] configuring, over-riding timeout values in testsuite

2006-09-21 Thread bkoz at gcc dot gnu dot org
--- Comment #7 from bkoz at gcc dot gnu dot org 2006-09-21 21:10 --- Whoops, Janis, you are right. Sorry for the false alarm. The fancy dejagnu line I spit out at you does nothing. I also tried to hack up this as you suggested: Index: testsuite/lib/libstdc++.exp

[Bug testsuite/28870] [4.2 Regression] configuring, over-riding timeout values in testsuite

2006-09-13 Thread bkoz at gcc dot gnu dot org
--- Comment #5 from bkoz at gcc dot gnu dot org 2006-09-13 06:26 --- Janis, this is how to set timeout on the make check command line: time make check RUNTESTFLAGS=-v -v -v -v --tool_opts timeout=300 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28870

[Bug testsuite/28870] [4.2 Regression] configuring, over-riding timeout values in testsuite

2006-09-13 Thread janis at gcc dot gnu dot org
--- Comment #6 from janis at gcc dot gnu dot org 2006-09-13 16:54 --- Benjamin, I had tried that, but it adds timeout=300 to the options passed to the compiler. Does it really work for you? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28870

[Bug testsuite/28870] [4.2 Regression] configuring, over-riding timeout values in testsuite

2006-09-12 Thread sje at cup dot hp dot com
--- Comment #2 from sje at cup dot hp dot com 2006-09-12 16:36 --- I wonder if it would be possible to implement something like 'dg-timeout 600' so that the timeout could be changed for just some tests and possibly just on some hosts by using the target option with dg-timeout. Most of

[Bug testsuite/28870] [4.2 Regression] configuring, over-riding timeout values in testsuite

2006-09-12 Thread janis at gcc dot gnu dot org
--- Comment #3 from janis at gcc dot gnu dot org 2006-09-12 23:23 --- I'm starting to figure out how all this works. A quick fix for now might be, as Benjamin suggested, for libstdc++.exp to only change the timeout value if it doesn't already exist. That could be done with if

[Bug testsuite/28870] [4.2 Regression] configuring, over-riding timeout values in testsuite

2006-09-12 Thread janis at gcc dot gnu dot org
--- Comment #4 from janis at gcc dot gnu dot org 2006-09-12 23:42 --- Mike, I added you to the cc: list because you know a lot about how DejaGnu is used with the GCC testsuite and undoubtedly have useful things to add to the discussion. -- janis at gcc dot gnu dot org changed:

[Bug testsuite/28870] [4.2 Regression] configuring, over-riding timeout values in testsuite

2006-09-01 Thread mmitchel at gcc dot gnu dot org
-- mmitchel at gcc dot gnu dot org changed: What|Removed |Added Priority|P3 |P2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28870

[Bug testsuite/28870] [4.2 Regression] configuring, over-riding timeout values in testsuite

2006-08-30 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-08-31 02:53 --- Confirmed, this is a regression. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added