search

kubevirt / csi-driver

KubeVirt CSI driver
Other
34 stars 25 forks source link

Run e2e in parallel (4 processes) #89

Closed awels closed 1 day ago

awels commented 12 months ago

What this PR does / why we need it: Modified running of the e2e to be parallell, defaulted to 4 concurrent processes. Use kubevirtci 1.25 instead of 1.26 until the centos 9 version stabilizes. After each failure immediately dump the cluster state so it is easier to investigate the failures.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged): Fixes #

Special notes for your reviewer:

Release note:

NONE
kubevirt-bot commented 12 months ago

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please ask for approval from awels. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/kubevirt/csi-driver/blob/main/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
awels commented 12 months ago

/test pull-csi-driver-sanity-test /test pull-csi-driver-split-e2e-k8s

awels commented 10 months ago

/test pull-csi-driver-e2e-k8s

awels commented 10 months ago

/test pull-csi-driver-e2e-k8s

awels commented 10 months ago

/test pull-csi-driver-split-e2e-k8s /test pull-csi-driver-e2e-k8s

awels commented 10 months ago

/test pull-csi-driver-sanity-test

awels commented 10 months ago

/test pull-csi-driver-sanity-test

awels commented 10 months ago

/test pull-csi-driver-split-k8s-suite-k8s

awels commented 10 months ago

/test pull-csi-driver-e2e-k8s

awels commented 10 months ago

/test pull-csi-driver-split-k8s-suite-k8s

awels commented 8 months ago

/test pull-csi-driver-split-k8s-suite-k8s

kubevirt-bot commented 5 months ago

@awels: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-csi-driver-split-k8s-suite-k8s c9d604e95749d6317c6283ca7e2e156ef1bca14e link true /test pull-csi-driver-split-k8s-suite-k8s
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
kubevirt-bot commented 5 months ago

PR needs rebase.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
kubevirt-bot commented 2 months ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kubevirt-bot commented 1 month ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

kubevirt-bot commented 1 day ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

kubevirt-bot commented 1 day ago

@kubevirt-bot: Closed this PR.

In response to [this](https://github.com/kubevirt/csi-driver/pull/89#issuecomment-2201305809): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.