fix(fvp): adjust lava-test-monitor timeout for fvp TFTF jobs
Curently, there is no timeout value for actions' lava-test-monitor,
thus LAVA defaults it to 30 seconds. This is an sensitive value
which defines the maximum allowed time for the testing phase (test
action, through monitors), with the consequence that currently LAVA
only test for 30 seconds [1], a value too short for TFTF testing. This
commit, defines this value to 45 minutes, enough time for all cases
seen so far, i.e. [2]. Also, it explictitly defines other relevant
timeout values, placing all these on top of job definition.
To take [1] and [2] as job examples, [1] within 30 seconds, is only
able to execute 3 tests, while [2] 137.
[1] https://tf.validation.linaro.org/scheduler/job/209121
[2] https://tf.validation.linaro.org/scheduler/job/207989
Signed-off-by: Leonardo Sandoval <leonardo.sandoval@linaro.org>
Change-Id: I475eb7f5aae28e50355a2a25881c21aa5c588e99
diff --git a/script/gen_fvp_tftf_yaml.sh b/script/gen_fvp_tftf_yaml.sh
index caf1d0a..99295f9 100755
--- a/script/gen_fvp_tftf_yaml.sh
+++ b/script/gen_fvp_tftf_yaml.sh
@@ -17,22 +17,38 @@
job_name: fvp-tftf-{MODEL}
timeouts:
+ job:
+ minutes: 60
+ action:
+ minutes: 50
+ actions:
+ auto-login-action:
+ seconds: 300
+ lava-test-monitor:
+ minutes: 45
+ lava-test-shell:
+ seconds: 300
+ lava-test-retry:
+ seconds: 300
+ http-download:
+ seconds: 120
+ download-retry:
+ seconds: 120
+ fvp-deploy:
+ seconds: 300
connection:
minutes: 3
connections:
+ lava-test-retry:
+ seconds: 300
lava-test-monitor:
- minutes: 10
- job:
- minutes: 60
- actions:
- auto-login-action:
- minutes: 5
- http-download:
- minutes: 2
- download-retry:
- minutes: 2
- fvp-deploy:
- minutes: 5
+ seconds: 300
+ lava-test-shell:
+ seconds: 300
+ bootloader-action:
+ seconds: 300
+ bootloader-retry:
+ seconds: 300
priority: medium
visibility: public
@@ -129,8 +145,6 @@
{BOOT_ARGUMENTS}
- test:
- timeout:
- minutes: 30
monitors:
- name: TFTF