Hi,
On Thursday 13 April 2017 08:14 PM, Denis HUMEAU wrote:
I’m trying to set one timeout per test in a job. To do so I’m declaring one test block per test.
I could see one test action in your job definition which has 60 minutes of timeout. That test action runs 4 tests. The timeout defined on the test action applies for the overall time the test action should complete within. It does not apply for each of the 4 tests that are defined.
Unfortunately, it seems that only the first timeout declaration is taken into account. Did I miss something in my job definition?
In order to have individual timeouts for each test, I would suggest defining multiple test actions, such as:
- test: metadata: format: Lava-Test Test Definition 1.0 name: DISK_AIO_STRESS-BENCHMARK description: "DISK_AIO_STRESS BENCHMARK tests " timeout: minutes: 30 definitions: #10 minutes - from: git repository: /local/dev/frq08954/dispatcher/lava-tests path: tests-def/benchmark/TC_BENCH_DISK_AIO_STRESS.yaml name: TC_BENCH_DISK_AIO_STRESS
- test: metadata: format: Lava-Test Test Definition 1.0 name: DISK_HDPARM_READ-BENCHMARK description: "DISK_HDPARM_READ BENCHMARK tests " timeout: minutes: 45 definitions: - from: git repository: /local/dev/frq08954/dispatcher/lava-tests path: tests-def/benchmark/TC_BENCH_DISK_HDPARM_READ.yaml name: TC_BENCH_DISK_HDPARM_READ
- test: metadata: format: Lava-Test Test Definition 1.0 name: BENCH_DISK_IOZONE_READ-BENCHMARK description: "BENCH_DISK_IOZONE_READ BENCHMARK tests " timeout: minutes: 15 definitions: - from: git repository: /local/dev/frq08954/dispatcher/lava-tests path: tests-def/benchmark/TC_BENCH_DISK_IOZONE_READ.yaml name: TC_BENCH_DISK_IOZONE_READ
Hope I got your question right.
Thank You.