GCC 4.2.1 : testsuite says WARNING: program timed out

GCC 4.2.1 : testsuite says WARNING: program timed out

[Dennis Clarke]

Is there a way to allow the testsuite to just run regardless of howlong it
takes?

I am getting "program timed out" warnings for multiple tests :

Running
/export/home/dclarke/build/gcc-4.2.1/gcc/testsuite/gcc.c-torture/compile/compile.exp
...
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c  -O1  (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c  -O2  (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c  -O3 -fomit-frame-pointer  (test
for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c  -O3 -g  (test for excess errors)
WARNING: program timed out.


-
Dennis Clarke

Re: GCC 4.2.1 : testsuite says WARNING: program timed out

[David Daney]

Dennis Clarke wrote:
> Is there a way to allow the testsuite to just run regardless of howlong it
> takes?
>
> I am getting "program timed out" warnings for multiple tests :
>
> Running
> /export/home/dclarke/build/gcc-4.2.1/gcc/testsuite/gcc.c-torture/compile/compile.exp
> ...
> WARNING: program timed out.
> FAIL: gcc.c-torture/compile/20001226-1.c  -O1  (test for excess errors)
> WARNING: program timed out.
> FAIL: gcc.c-torture/compile/20001226-1.c  -O2  (test for excess errors)
> WARNING: program timed out.
> FAIL: gcc.c-torture/compile/20001226-1.c  -O3 -fomit-frame-pointer  (test
> for excess errors)
> WARNING: program timed out.
> FAIL: gcc.c-torture/compile/20001226-1.c  -O3 -g  (test for excess errors)
> WARNING: program timed out.
>
>   
You need a faster computer.  Those tests take a long time.  On slow 
systems they take longer than the default testsuite timeout to compile.  
You can probably safely ignore time outs for 20001226-1.c

David Daney

Re: GCC 4.2.1 : testsuite says WARNING: program timed out

[Dennis Clarke]

> Dennis Clarke wrote:
>> Is there a way to allow the testsuite to just run regardless of howlong it
>> takes?
>>
>> I am getting "program timed out" warnings for multiple tests :
>>
>> Running
>> /export/home/dclarke/build/gcc-4.2.1/gcc/testsuite/gcc.c-torture/compile/compile.exp
>> ...
>> WARNING: program timed out.
>> FAIL: gcc.c-torture/compile/20001226-1.c  -O1  (test for excess errors)
>> WARNING: program timed out.
>> FAIL: gcc.c-torture/compile/20001226-1.c  -O2  (test for excess errors)
>> WARNING: program timed out.
>> FAIL: gcc.c-torture/compile/20001226-1.c  -O3 -fomit-frame-pointer  (test
>> for excess errors)
>> WARNING: program timed out.
>> FAIL: gcc.c-torture/compile/20001226-1.c  -O3 -g  (test for excess errors)
>> WARNING: program timed out.
>>
>>
> You need a faster computer.

  Trust me .. I know.  :-)

  I do have access to top of the line Sun gear but I am running this
  experiment and this bootstrap on this machine.

  Thus, the question stands :

    Is there a way to allow the testsuite to just run regardless of
    how long it takes?


Dennis

RE: GCC 4.2.1 : testsuite says WARNING: program timed out

[Rupert Wood]

Dennis Clarke wrote:

>    Is there a way to allow the testsuite to just run regardless of
>    how long it takes?

I think you need to pass "set timeout -1" into dejagnu. I'd suggest a larger positive timeout instead.

I forget the correct way to do this - I used to end up editing the .exp files in /usr/share/dejagnu.

Rup.



______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

Re: GCC 4.2.1 : testsuite says WARNING: program timed out

[Christian Joensson]

2007/8/1, Rupert Wood <me@rupey.net>:
> Dennis Clarke wrote:
>
> >    Is there a way to allow the testsuite to just run regardless of
> >    how long it takes?
>
> I think you need to pass "set timeout -1" into dejagnu. I'd suggest a larger positive timeout instead.
>
> I forget the correct way to do this - I used to end up editing the .exp files in /usr/share/dejagnu.

that's right, however, I recall some issues with, e.g., libstdc++
testsuite not using the system set in, if memory serves me right,
remote.exp.

-- 
Cheers,

/ChJ

RE: GCC 4.2.1 : testsuite says WARNING: program timed out

[Dennis Clarke]

> Dennis Clarke wrote:
>
>>    Is there a way to allow the testsuite to just run regardless of
>>    how long it takes?
>
> I think you need to pass "set timeout -1" into dejagnu. I'd suggest a larger
> positive timeout instead.
>
> I forget the correct way to do this - I used to end up editing the .exp
> files in /usr/share/dejagnu.

okay .. that sounds like a good hint.

Well .. the file in the default share/dejagnu directory look like so :


$ ls
baseboards     framework.exp  mondfe.exp     standard.exp   testglue.c
config         ftp.exp        remote.exp     stub-loader.c  tip.exp
debugger.exp   kermit.exp     rlogin.exp     target.exp     util-defs.exp
dejagnu.exp    libexec        rsh.exp        targetdb.exp   utils.exp
dg.exp         libgloss.exp   runtest.exp    telnet.exp     xsh.exp
$


somehow .. that can not be right.  Let's look in the GCC 4.2.1 objdir area
for files that end with .exp :

$ cd gcc-4.2.1-build
$ find . -type f | grep "\.exp"
./gcc/testsuite/gcc/site.exp
./gcc/site.exp
$

okay .. now we are getting somewhere.  Maybe :-\

$ cat ./gcc/testsuite/gcc/site.exp
## these variables are automatically generated by make ##
# Do not edit here. If you wish to override these values
# add them to the last section
set rootme "/opt/build/gcc-4.2.1-build/gcc"
set srcdir "/export/home/dclarke/build/gcc-4.2.1/gcc"
set host_triplet sparc-sun-solaris2.8
set build_triplet sparc-sun-solaris2.8
set target_triplet sparc-sun-solaris2.8
set target_alias sparc-sun-solaris2.8
set libiconv "/export/home/dclarke/local/lib/libiconv.so
-R/export/home/dclarke/local/lib"
set CFLAGS ""
set CXXFLAGS ""
set HOSTCC "cc"
set HOSTCFLAGS "-g"
set TESTING_IN_BUILD_TREE 1
set HAVE_LIBSTDCXX_V3 1
set tmpdir /opt/build/gcc-4.2.1-build/gcc/testsuite/gcc
set srcdir "${srcdir}/testsuite"
## All variables above are generated by configure. Do Not Edit ##
$

there is not much there that looks helpful ... and both those files look to
be the same :

$ ls -li ./gcc/testsuite/gcc/site.exp ./gcc/site.exp
    263449 -rw-r--r--   1 dclarke  csw          759 Jul 31 20:58 ./gcc/site.exp
   1282849 -rw-r--r--   1 dclarke  csw          763 Jul 31 20:58
./gcc/testsuite/gcc/site.exp

$ diff ./gcc/testsuite/gcc/site.exp ./gcc/site.exp
17c17
< set tmpdir /opt/build/gcc-4.2.1-build/gcc/testsuite/gcc
---
> set tmpdir /opt/build/gcc-4.2.1-build/gcc/testsuite
$

great ... so then ... perhaps I do have to go back to the exp files in the
default dejagnu area ?

oh to heck with this ... perhaps I can tar up the whole objdir and move it
over to a 1.6GHz UltraSparc box and test it there .. but that defeats the
purpose.

Thanks for trying

Dennis

Re: GCC 4.2.1 : testsuite says WARNING: program timed out

[Rask Ingemann Lambertsen]

On Wed, Aug 01, 2007 at 03:57:19AM -0400, Dennis Clarke wrote:

> WARNING: program timed out.
> FAIL: gcc.c-torture/compile/20001226-1.c  -O1  (test for excess errors)

   It's in the archives:
<URL:http://gcc.gnu.org/ml/gcc/2006-09/msg00155.html>

-- 
Rask Ingemann Lambertsen

RE: GCC 4.2.1 : testsuite says WARNING: program timed out

[Dave Korn]

On 01 August 2007 16:00, Dennis Clarke wrote:

>> Dennis Clarke wrote:
>> 
>>>    Is there a way to allow the testsuite to just run regardless of
>>>    how long it takes?
>> 
>> I think you need to pass "set timeout -1" into dejagnu. I'd suggest a
>> larger positive timeout instead. 
>> 
>> I forget the correct way to do this - I used to end up editing the .exp
>> files in /usr/share/dejagnu.
> 
> okay .. that sounds like a good hint.
> 
> Well .. the file in the default share/dejagnu directory look like so :
> 
> 
> $ ls
> baseboards     framework.exp  mondfe.exp     standard.exp   testglue.c
 ^^^^^^^^^^^^

  You want baseboards/unix.exp.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....