Commit 8c4562be authored by Mylène Josserand's avatar Mylène Josserand Committed by Guillaume Tucker

Add a way to customize failure_retry variable

Add the possibility to set the "failure_retry" parameters
into the device dictionnary in case we would like to
re-test all the failing jobs (with "infrastructure_error" or
"job_error_exception")
Signed-off-by: Mylène Josserand's avatarMylène Josserand <mylene.josserand@collabora.com>
parent f5afadbc
Pipeline #20907 passed with stage
in 1 minute and 6 seconds
......@@ -147,6 +147,9 @@ constants:
# avoid setting searchwindowsize:
# Data before searchwindowsize point is preserved, but not searched.
spawn_maxread: '{{ spawn_maxread | default(4092) }}'
# Set the failure retry to default or override it
failure_retry: {{ failure_retry|default('1') }}
{% endblock constants -%}
{% block commands %}
......
......@@ -75,6 +75,7 @@ CONTEXT_VARIABLES = [
"custom_kernel_args",
"extra_kernel_args",
"extra_nfsroot_args",
"failure_retry",
"kernel_loglevel",
"kernel_start_message",
"lava_test_results_dir",
......
......@@ -142,6 +142,9 @@ class Pipeline:
subdict_merge_get(timeouts, "connections", action.name)
)
# retrieve the failure_retry constant variable
action.max_retries = action.get_constant("failure_retry", "")
action.parameters = parameters
def describe(self, verbose=True):
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment