* How do I run dejagnu's runtest with other timeout value for specific tests in gcc's testsuite?
@ 2002-10-21 16:13 Christian Jönsson
2002-10-22 3:18 ` Ben Elliston
0 siblings, 1 reply; 3+ messages in thread
From: Christian Jönsson @ 2002-10-21 16:13 UTC (permalink / raw)
To: gcc
I might sound a bit stupid here but hey, I'll take the chance then...
How do you run the testsuite, let's say a specific test, with a
timeout that's not the default, i.e., the value set in the dejagnu
files?
I'm thnking of something like this:
make check-gcc RUNTESTFLAGS="gcc.c-torture/compile.exp=20001226-1* other-options"
can I for example set timeout = 600 somehow as other-options?
Tha problem is that I get timeouts like this:
=== gcc tests ===
Running target unix
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c, -O1
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c, -O2
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c, -O3 -fomit-frame-pointer
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c, -O3 -g
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c, -Os
that I would like to see if they are due to my system being too old or
if it's simply not ever coming to a halt...
From the log file, I see the following:
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/20001226-1.o /usr/local/src/gcc-binutils/trunk/gcc-binutils/gcc/testsuite/gcc.c-torture/compile/20001226-1.c (timeout = 300)
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/20001226-1.o /usr/local/src/gcc-binutils/trunk/gcc-binutils/gcc/testsuite/gcc.c-torture/compile/20001226-1.c (timeout = 300)
WARNING: program timed out.
compiler exited with status 1
FAIL: gcc.c-torture/compile/20001226-1.c, -O1
etc.
Cheers,
/ChJ
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How do I run dejagnu's runtest with other timeout value for specific tests in gcc's testsuite?
2002-10-21 16:13 How do I run dejagnu's runtest with other timeout value for specific tests in gcc's testsuite? Christian Jönsson
@ 2002-10-22 3:18 ` Ben Elliston
2002-10-22 14:15 ` Christian Jönsson
0 siblings, 1 reply; 3+ messages in thread
From: Ben Elliston @ 2002-10-22 3:18 UTC (permalink / raw)
To: gcc
>>>>> "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
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: How do I run dejagnu's runtest with other timeout value for specific tests in gcc's testsuite?
2002-10-22 3:18 ` Ben Elliston
@ 2002-10-22 14:15 ` Christian Jönsson
0 siblings, 0 replies; 3+ messages in thread
From: Christian Jönsson @ 2002-10-22 14:15 UTC (permalink / raw)
To: 'Ben Elliston', gcc
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-10-22 18:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-21 16:13 How do I run dejagnu's runtest with other timeout value for specific tests in gcc's testsuite? Christian Jönsson
2002-10-22 3:18 ` Ben Elliston
2002-10-22 14:15 ` Christian Jönsson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).