e2e: enable fail-fast to abort suite on first test failure#6088
Conversation
Configure Ginkgo's FailFast option so that when any spec fails, all remaining specs are skipped immediately instead of continuing to run the rest of the suite. Signed-off-by: Rakshith R <rar@redhat.com>
|
/test ci/centos/mini-e2e/k8s-1.34 |
890b29c to
e4e615e
Compare
|
/test ci/centos/mini-e2e/k8s-1.34/rbd |
|
Have you considered passing |
We anyway need all testcases to pass to merge pr, therefore it makes sense to enable it by default in code ? The functionality is the same but it would again scatter the configurations IMO. |
|
@Mergifyio queue |
Merge Queue StatusRule:
This pull request spent 2 hours 49 minutes 40 seconds in the queue, including 2 hours 49 minutes 30 seconds running CI. Required conditions to merge
ReasonThe merge conditions cannot be satisfied due to failing checks Failing checks: HintYou may have to fix your CI before adding the pull request to the queue again. |
failed due to ci flake adding skip-ci label. |
|
@Mergifyio requeue |
Merge Queue StatusRule:
This pull request spent 1 hour 36 minutes 35 seconds in the queue, including 5 minutes 14 seconds running CI. Required conditions to merge
|
Describe what this PR does
Configure Ginkgo's FailFast option so that when any spec fails,
all remaining specs are skipped immediately instead of continuing
to run the rest of the suite.
Saves a lot of ci resources.
Example run
https://jenkins-ceph-csi.apps.ocp.cloud.ci.centos.org/blue/organizations/jenkins/mini-e2e_k8s-1.34/detail/mini-e2e_k8s-1.34/567/pipeline/
Checklist:
guidelines in the developer
guide.
Request
notes
updated with breaking and/or notable changes for the next major release.
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>: retest the<job-name>after unrelatedfailure (please report the failure too!)