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

[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
===================================================================
--- testsuite/lib/libstdc++.exp (revision 117118)
+++ testsuite/lib/libstdc++.exp (working copy)
@@ -350,8 +350,14 @@
     }

     lappend options "compiler=$cxx_final"
-    lappend options "timeout=600"

+    # This is a hack to set the timeout higher.
+    if [target_info exists gcc,timeout] {
+        lappend options "timeout=[target_info gcc,timeout]"
+    } else {
+        lappend options "timeout=600"
+    }
+
     return [target_compile $source $dest $type $options]
 }

However, I'm not quite sure how to test that people can over-ride timeout now.

Can any testsuite maintainer help please? Just some clear directions on how to
do this stuff would be appreciated. 

-benjamin


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28870