From: Simon Marchi <simon.marchi@efficios.com>
Date: Tue, 2 May 2023 19:16:40 +0000 (-0400)
Subject: jjb: binutils-gdb: use absolute 3 hours job timeout
X-Git-Url: https://git.lttng.org./?a=commitdiff_plain;h=1bba86a0c285533ddc1879d4d582569058fde79b;p=lttng-ci.git

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 134aec4..9a2d552 100644
--- 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