jjb: binutils-gdb: use absolute 3 hours job timeout
authorSimon Marchi <simon.marchi@efficios.com>
Tue, 2 May 2023 19:16:40 +0000 (15:16 -0400)
committerSimon Marchi <simon.marchi@efficios.com>
Tue, 2 May 2023 19:18:33 +0000 (15:18 -0400)
commit1bba86a0c285533ddc1879d4d582569058fde79b
treea99d7c3d4cfb4b0061654618817754f6aa7e587c
parent2c34ea1488ea3241038be5ef41a099ea14d42041
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
jobs/binutils-gdb.yaml
This page took 0.023293 seconds and 4 git commands to generate.