Here's a patch we've been using in Debian for some time. The
hardcoded "300" timeout is too small for various testsuites on some of
our slower architectures. Instead of bravely attempting to clean up
the million settings of "timeout", this patch just overrides the
one that was giving us trouble; posted for your consideration
regardless.
--
Daniel Jacobowitz
CodeSourcery
2008-04-06 Daniel Jacobowitz <[EMAIL PROTECTED]>
* lib/remote.exp (remote_exec): Check the DEJAGNU_TIMEOUT environment
variable.
Index: dejagnu-1.4.4.cvs20060709/lib/remote.exp
===================================================================
--- dejagnu-1.4.4.cvs20060709.orig/lib/remote.exp 2006-07-09
15:23:01.000000000 -0400
+++ dejagnu-1.4.4.cvs20060709/lib/remote.exp 2006-07-09 15:23:23.000000000
-0400
@@ -251,6 +251,8 @@ proc remote_exec { hostname program args
# 300 is probably a lame default.
if { [llength $args] > 3 } {
set timeout "[lindex $args 3]"
+ } elseif { [getenv DEJAGNU_TIMEOUT] != "" } {
+ set timeout [getenv DEJAGNU_TIMEOUT]
} else {
set timeout 300
}
_______________________________________________
DejaGnu mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/dejagnu
