LAVA actions follow a hierarchical structure, where most subactions have their timeouts overridden if the parent action supports a retry mechanism, such as the `depthcharge-retry` action. The timeout is calculated as: [1] ``` parent action timeout / failure_retry value ``` To adjust a subaction's timeout, we need to modify the nearest parent action. [1] https://gitlab.collabora.com/lava/lava/-/blob/collabora/production/lava_dispatcher/action.py#L149 Signed-off-by: Guilherme Gallo <guilherme.gallo@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/33906>
67 lines
1.4 KiB
YAML
67 lines
1.4 KiB
YAML
job_name: 'test-project: my_pipeline_info'
|
|
device_type: my_uboot_device_type
|
|
visibility:
|
|
group:
|
|
- my_visibility_group
|
|
priority: 75
|
|
context:
|
|
extra_nfsroot_args: ' init=/init rootwait usbcore.quirks=0bda:8153:k'
|
|
timeouts:
|
|
job:
|
|
minutes: 10
|
|
actions:
|
|
depthcharge-retry:
|
|
minutes: 6
|
|
depthcharge-action:
|
|
minutes: 5
|
|
uboot-action:
|
|
seconds: 200
|
|
actions:
|
|
- deploy:
|
|
timeout:
|
|
minutes: 5
|
|
to: tftp
|
|
os: oe
|
|
kernel:
|
|
url: None/None
|
|
nfsrootfs:
|
|
url: None
|
|
compression: zstd
|
|
format: tar
|
|
overlays: {}
|
|
dtb:
|
|
url: None/my_dtb_filename.dtb
|
|
- boot:
|
|
failure_retry: 2
|
|
method: u-boot
|
|
prompts:
|
|
- 'lava-shell:'
|
|
commands: nfs
|
|
- test:
|
|
timeout:
|
|
minutes: 10
|
|
failure_retry: 1
|
|
definitions:
|
|
- name: mesa
|
|
from: inline
|
|
lava-signal: kmsg
|
|
path: inline/mesa.yaml
|
|
repository:
|
|
metadata:
|
|
name: mesa
|
|
description: Mesa test plan
|
|
os:
|
|
- oe
|
|
scope:
|
|
- functional
|
|
format: Lava-Test Test Definition 1.0
|
|
run:
|
|
steps:
|
|
- echo test UBOOT
|
|
- export CURRENT_SECTION=dut_boot
|
|
- set -e
|
|
- echo Could not find jwt file, disabling S3 requests...
|
|
- sed -i '/S3_RESULTS_UPLOAD/d' /set-job-env-vars.sh
|
|
- sleep 1
|
|
- lava-test-case 'test-project_dut' --shell /init-stage2.sh
|