lava-templates/fvp-*: Decrease test timeout to 12min
This timeout kicks in when the test fails expectations (i.e. it keeps
waiting for a particular output, but as it doesn't arrive, it keeps
waiting until timeout). Recently we had a case when a lot of test jobs
started to fail like that at the same time (apparently because of influx
of new patches), which caused a bottleneck in LAVA queue, which in turn
lead to domino effect on Jenkins side, which jobs bottlenecking and
timing out.
Based on job log, the maximum runtime we have is 10-11 minutes. So,
cut down the timeout to 12 min (25% decrease), which should alleviate
bottlenecking issue at least somewhat, until a more flexible solution
is found.
Related to https://linaro.atlassian.net/browse/TFC-368
Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
Change-Id: I6738ae266a725b7399ab8564141ce77c0183c880
diff --git a/script/lava-templates/fvp-linux.yaml b/script/lava-templates/fvp-linux.yaml
index 6187e14..eb0a233 100644
--- a/script/lava-templates/fvp-linux.yaml
+++ b/script/lava-templates/fvp-linux.yaml
@@ -25,7 +25,7 @@
lava-test-monitor:
minutes: 5
lava-test-interactive:
- minutes: 15
+ minutes: 12
lava-test-shell:
seconds: 300
http-download:
diff --git a/script/lava-templates/fvp-tftf.yaml b/script/lava-templates/fvp-tftf.yaml
index 0e49171..664898d 100644
--- a/script/lava-templates/fvp-tftf.yaml
+++ b/script/lava-templates/fvp-tftf.yaml
@@ -23,7 +23,7 @@
lava-test-monitor:
minutes: 7
lava-test-interactive:
- minutes: 15
+ minutes: 12
lava-test-shell:
seconds: 300
lava-test-retry: