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 testsuite timeout question (gcc.c-torture/compile/20001226-1.c)


On Tue, Sep 05, 2006 at 01:27:45PM -0700, Steve Ellcey wrote:

> I am not sure what the 'right' way to do this is.  I wound up editing
> /usr/share/dejagnu/remote.exp to change 'set timeout 300' to 'set
> timeout 2000' and I edited /usr/share/dejagnu/config/unix.exp to change
> 'set status [remote_wait $dest 300]' to 'set status [remote_wait $dest
> 2000]'

   It helps some. I tried this at the end of
/usr/share/dejagnu/baseboards/unix.exp:

set_board_info gcc,timeout 5400
set_board_info g++,timeout 5400
set_board_info gfortran,timeout 5400
[and so on for any x in "=== x tests ===" from the summary]

   Additionally, these changes as per your suggestion:

--- /usr/share/dejagnu/config/unix.exp-orig	2005-03-05 21:06:49.000000000 +0100
+++ /usr/share/dejagnu/config/unix.exp	2006-09-06 19:27:27.000000000 +0200
@@ -81 +81 @@
-	    set status [remote_wait $dest 300]
+	    set status [remote_wait $dest 5300]
--- /usr/share/dejagnu/remote.exp-orig	2005-03-05 21:06:49.000000000 +0100
+++ /usr/share/dejagnu/remote.exp	2006-09-06 19:28:30.000000000 +0200
@@ -260 +260 @@
-	set timeout 300
+	set timeout 5500

   With the above changes, the following timeouts are used according to the
log files for the following tests:

5500 seconds:
libffi, libgomp, libjava, g++, gfortran and objc
libmudflap for anything not using a 10 or 20 second timeout
libstdc++ when
	executing msgfmt, extract_symvers, 
	compiling libstdc++-v3/testsuite/19_diagnostics/23591_thread-1.c,
	iconv7593.c, function7593.c and cxaatexit7593.cc

gcc when
	compiling and executing gcc/testsuite/gcc/gcc.dg-struct-layout-1
	compiling tls12629.c, tls_runtime12629.c
	running 'spawn --help'
	executing gcc/gcov
	running 'gcc/xgcc -v'

5400 seconds:
gcc for anything not using the timeout of 5500 seconds

5300 seconds:
(nothing)

600 seconds:
libstdc++ for anything not using the timeout of 5500 seconds

20 seconds:
libmudflap
	libmudflap.cth/pass40-frag.c execution and output pattern tests

10 seconds:
libmudflap
	libmudflap.cth/pass37-frag.c and libmudflap.cth/pass39-frag.c
	execution and output pattern tests

-- 
Rask Ingemann Lambertsen


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