ci: work around LAVA timeout regression
A change to LAVA's timeout priorities has caused a regression for some
of our monitor tests, which now fail on the global timeout instead of
their designated local timeout.
This work-around increases the global monitor timeout to the maximum of
all of the monitor tests of jobs that we know to be impacted currently,
but more will no doubt follow.
Regressive change: https://gitlab.com/lava/lava/-/commit/34769f3c5f118f0afa6e6afd1c618e3c94514939
Signed-off-by: Chris Kay <chris.kay@arm.com>
Change-Id: Id53135364cd1e65675d66cc635d840ec069685ef
diff --git a/script/lava-templates/juno-tftf.yaml b/script/lava-templates/juno-tftf.yaml
index 9eae847..b96c4d1 100644
--- a/script/lava-templates/juno-tftf.yaml
+++ b/script/lava-templates/juno-tftf.yaml
@@ -9,8 +9,10 @@
job:
minutes: 45
actions:
- lava-test-monitor:
- seconds: 120
+# lava-test-monitor:
+# seconds: 120
+ lava-test-monitor: # See change Id53135364cd1e65675d66cc635d840ec069685ef
+ minutes: 30
connections:
lava-test-monitor:
seconds: 120