You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
FYI @pshipton @JasonFengJ9
The text was updated successfully, but these errors were encountered: