File: allow-to-define-timeout-via-envvar.diff

package info (click to toggle)
dejagnu 1.6.3-1.1
  • links: PTS
  • area: main
  • in suites: trixie
  • size: 2,956 kB
  • sloc: exp: 11,235; sh: 5,264; tcl: 405; ansic: 369; makefile: 224; awk: 175; cpp: 92; python: 59; sql: 38
file content (25 lines) | stat: -rw-r--r-- 975 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
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
     }