Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restart failed conformance tests in E2E tests #3287

Open
xmudrii opened this issue Jun 28, 2024 · 0 comments
Open

Restart failed conformance tests in E2E tests #3287

xmudrii opened this issue Jun 28, 2024 · 0 comments
Labels
kind/flake Categorizes issue or PR as related to a flaky test. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.
Milestone

Comments

@xmudrii
Copy link
Member

xmudrii commented Jun 28, 2024

Description of the feature you would like to add / User story

We often face issue where a couple of conformance tests fail due to the unstable infrastructure. This fails the whole E2E job and we have to restart it which takes a lot of time and resources, and especially slows down the testing phase.

Solution details

If there are failed conformance tests in the E2E tests, those tests should be restarted once or twice to rule out potential infrastructure instability issues. A very basic implementation of this has been done in #3261

Alternative approaches

/retest

Use cases

Significantly speeds up the KubeOne testing phase (potentially talking about hours). 🚀

@xmudrii xmudrii added kind/flake Categorizes issue or PR as related to a flaky test. priority/high sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. labels Jun 28, 2024
@xmudrii xmudrii added this to the KubeOne 1.9 milestone Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.
Projects
None yet
Development

No branches or pull requests

2 participants