Auto rerun FAILURE state test jobs in test pipeline
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
We support auto-rerun failed tests in the test pipeline (see #3431). It is useful for triaging and rerunning the failed tests automatically. However, this feature requires the test jobs to run to the completion (to get the failed test names). If the test jobs are in the `FAILURE` state (i.e., machine disconnected, machine out of space, etc), someone still needs to restart the jobs manually. This is very tedious during release time. We should have a feature to Auto rerun FAILURE state test jobs.
TRSS should support displaying the rerun test jobs. We should auto-archive the rerun jobs TAP into the parent job.
To simplify this, we will add this to the parent test job. This means a parent test job may trigger the following child test jobs:
- parallel child test jobs
- rerun job for failed tests
- rerun job(s) for FAILURE child test job(s)
FYI @pshipton @JasonFengJ9
Contributor guide
Research direction
Start with the existing auto-rerun implementation referenced in #3431 and trace the parent test job flow. Check how TRSS displays child jobs and how TAP is archived; done means FAILURE child jobs are rerun automatically, their TAP is archived into the parent job, and the reruns are visible.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100