Hello, Please consider allowing custom timeout environment variable for slow architectures, such m68k. The following change we carry in Debian distribution:
Description: timeout for m68k and maybe arm should be doubled The timeout in /usr/share/dejagnu/remote.exp:257 is too short for many of gcc's testcases, when run on m68k and arm. Include a hack to define a specific timeout via an environment variable. --- The information above should follow the Patch Tagging Guidelines, please checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here are templates for supplementary fields that you might want to add: Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=182177 Bug-Debian: https://bugs.debian.org/182177 Last-Update: 2021-05-03 --- dejagnu-1.6.2.orig/lib/remote.exp +++ dejagnu-1.6.2/lib/remote.exp @@ -311,6 +311,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 } Thanks for considering! Regards -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-. _______________________________________________ Bug-dejagnu mailing list Bug-dejagnu@gnu.org https://lists.gnu.org/mailman/listinfo/bug-dejagnu
