jjb: binutils-gdb: use absolute 3 hours job timeout

The no-activity timeout mode is not good for when a commit completely
breaks GDB.  All tests in the testsuite will just fail very slowly
(timing out), but they will still print lines regularly.  So the timeout
will never actually kick in.  Change the timeout to be fixed at 3
hours.

Change-Id: I6606b5ed02cb7deed7491179aa6f1fc40e017480

diff --git a/jobs/binutils-gdb.yaml b/jobs/binutils-gdb.yaml
index 134aec48fe34c0aec7b64f25aff4b858e22727ba..9a2d552373781a919c50a647df9d5700940e8f9e 100644 (file)
--- a/jobs/binutils-gdb.yaml
+++ b/jobs/binutils-gdb.yaml
@@ -11,9 +11,9 @@
       - ansicolor:
           colormap: gnome-terminal
       - timeout:
-          timeout: 20
+          timeout: 180
           fail: true
-          type: no-activity
+          type: absolute
           write-description: "<h1 style=\"color:red\">This build failed due to timeout.</h1>"
       - timestamps
       - workspace-cleanup