Project

General

Profile

Actions

action #104007

closed

coordination #102906: [saga][epic] Increased stability of tests with less "known failures", known incompletes handled automatically within openQA

Support retry of openQA jobs based on test variables

Added by okurz over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2021-12-15
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Similar as in https://docs.microsoft.com/en-us/azure/devops/release-notes/2021/sprint-195-update#automatic-retries-for-a-task and https://docs.gitlab.com/ee/ci/yaml/#retry and https://github.com/marketplace/actions/retry-step

Acceptance criteria

  • AC1: openQA jobs are automatically retriggered with a maximum amount specified in test variables
  • AC2: By default openQA tests apply no automatic retry

Acceptance tests

  • AT1-1: Given an unfinished openQA test with the special RETRY variable given with value N When the job fails And the current job is not already the N-th clone of an original job Then an automatic clone is created
  • AT1-2: Given an unfinished openQA test with the special RETRY variable given with value N When the job fails And the current job is the N-th clone of an original job Then no automatic clone is created
  • AT2-1: Given an unfinished openQA test with no special retry variable given When the job fails Then no automatic clone is created at this point (job done hooks or external events may still trigger clones as well as manual triggers)

Related issues 1 (1 open0 closed)

Related to openQA Project - action #113758: Jobs restarted with `RETRY` are not shown as 'clones', so it is hard or impossible find the original jobNew2022-07-18

Actions
Actions

Also available in: Atom PDF