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

[Feature] Support running flaky-tests N times before marking them failed #2208

Open
1 task done
rahulait opened this issue Dec 10, 2024 · 0 comments
Open
1 task done
Labels
enhancement New feature or request

Comments

@rahulait
Copy link

Problem Statement

We are planning to use chainsaw for our k8s testing. We have e2e tests written in go which do a lot of system testing using k8s. Since these tests work with a bunch of systems, things can sometimes go wrong due to flakiness in environment. For example, if API is being upgraded and the tests are trying to reach to API or requests are getting rate-limited etc. If a test fails due to some reason, we would like to re-run it automatically just to see if it passes the next time or not than requiring someone to manually trigger tests again. We would like to do this only for the tests which have failed. Chainsaw does have a flag --repeat-count=N but that always runs the test N number of times (irrespective of failure). We would like to have something similar to what ginkgo has (ginkgo.flake-attempts=N) so that flaky tests can be auto-retried.

Solution Description

Similar to --repeat-count, add a flag --flake-attempts or --repeat-failed-count which will make the failed test run max N times or until it succeeds.

Alternatives

No response

Additional Context

No response

Slack discussion

https://kubernetes.slack.com/archives/C067LUFL43U/p1733811046564419

Research

  • I have searched other issues in this repository and mine is not recorded.
@rahulait rahulait added the enhancement New feature or request label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant