RE: How do I run dejagnu's runtest with other timeout value for specific tests in gcc's testsuite?

[Christian Jönsson <christian at j-son dot org>]

Thanks, that solved the gcc issues I had in

http://gcc.gnu.org/ml/gcc-testresults/2002-10/msg00714.html

I can now confirm, with timeout=1200, that the 20001226 tests all pass,
they seem to blow up with optimisation turned on...

Executing on host: /share1/gcc-dev/objdir/gcc/xgcc
-B/share1/gcc-dev/objdir/gcc/
  -w  -O0   -c  -o
/usr/local/src/gcc-binutils/trunk/objdir/gcc/testsuite/200012
26-1.o
/usr/local/src/gcc-binutils/trunk/gcc-binutils/gcc/testsuite/gcc.c-tortu
r
e/compile/20001226-1.c    (timeout = 1200)
PASS: gcc.c-torture/compile/20001226-1.c,  -O0
Executing on host: /share1/gcc-dev/objdir/gcc/xgcc
-B/share1/gcc-dev/objdir/gcc/
  -w  -O1   -c  -o
/usr/local/src/gcc-binutils/trunk/objdir/gcc/testsuite/200012
26-1.o
/usr/local/src/gcc-binutils/trunk/gcc-binutils/gcc/testsuite/gcc.c-tortu
r
e/compile/20001226-1.c    (timeout = 1200)
PASS: gcc.c-torture/compile/20001226-1.c,  -O1
Executing on host: /share1/gcc-dev/objdir/gcc/xgcc
-B/share1/gcc-dev/objdir/gcc/
  -w  -O2   -c  -o
/usr/local/src/gcc-binutils/trunk/objdir/gcc/testsuite/200012
26-1.o
/usr/local/src/gcc-binutils/trunk/gcc-binutils/gcc/testsuite/gcc.c-tortu
r
e/compile/20001226-1.c    (timeout = 1200)
PASS: gcc.c-torture/compile/20001226-1.c,  -O2
Executing on host: /share1/gcc-dev/objdir/gcc/xgcc
-B/share1/gcc-dev/objdir/gcc/
  -w  -O3 -fomit-frame-pointer   -c  -o
/usr/local/src/gcc-binutils/trunk/objdir
/gcc/testsuite/20001226-1.o
/usr/local/src/gcc-binutils/trunk/gcc-binutils/gcc/t
estsuite/gcc.c-torture/compile/20001226-1.c    (timeout = 1200)
PASS: gcc.c-torture/compile/20001226-1.c,  -O3 -fomit-frame-pointer
Executing on host: /share1/gcc-dev/objdir/gcc/xgcc
-B/share1/gcc-dev/objdir/gcc/
  -w  -O3 -g   -c  -o
/usr/local/src/gcc-binutils/trunk/objdir/gcc/testsuite/200
01226-1.o
/usr/local/src/gcc-binutils/trunk/gcc-binutils/gcc/testsuite/gcc.c-tor
ture/compile/20001226-1.c    (timeout = 1200)
PASS: gcc.c-torture/compile/20001226-1.c,  -O3 -g
Executing on host: /share1/gcc-dev/objdir/gcc/xgcc
-B/share1/gcc-dev/objdir/gcc/
  -w  -Os   -c  -o
/usr/local/src/gcc-binutils/trunk/objdir/gcc/testsuite/200012
26-1.o
/usr/local/src/gcc-binutils/trunk/gcc-binutils/gcc/testsuite/gcc.c-tortu
r
e/compile/20001226-1.c    (timeout = 1200)
PASS: gcc.c-torture/compile/20001226-1.c,  -Os
testcase
/usr/local/src/gcc-binutils/trunk/gcc-binutils/gcc/testsuite/gcc.c-tort
ure/compile/compile.exp completed in 4879 seconds

However, in libjava, I get SyncTest timeouts, and in libstdc++-v3, I get
pthread timeouts, as you can see in the above mentioned posting.

Any hint on what to set and where to set it?

Cheers,

/ChJ

-----Original Message-----
From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@gcc.gnu.org] On Behalf Of
Ben Elliston
Sent: Tuesday, October 22, 2002 7:13 AM
To: gcc@gcc.gnu.org
Subject: Re: How do I run dejagnu's runtest with other timeout value for
specific tests in gcc's testsuite?


>>>>> "nsson" == nsson  <Christian> writes:

  nsson> I might sound a bit stupid here but hey, I'll take the chance
  nsson> then...

When it comes to DejaGnu, there are few stupid questions. ;-)

  nsson> How do you run the testsuite, let's say a specific test, with
  nsson> a timeout that's not the default, i.e., the value set in the
  nsson> dejagnu files?

There are two timeouts relevant to GCC testing: a compile-time timeout
and a runtime timeout -- both can be controlled.  If you are just doing
native testing (as it sounds like you are), then you can try adding
these lines to your `unix.exp' baseboard definition file:

     set_board_info gcc,timeout 600
     set_board_info sim,timeout 600

There's a chance that this won't work (as DejaGnu is, umm, a real
joy) -- but I hope this will get you on the right track.

Cheers, Ben