-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Enable periodic integration tests in prow #19051
Comments
I am happy to take it! |
/assign @manthanguptaa |
Hi @ivanvc, Thank you! |
@kishen-v I am still working on it. Thanks |
Hi @manthanguptaa, are you still working on this task? Please let me know so we can reassign it. Thanks :) |
Hey @ivanvc! yes, I have yet to get on this and will soon enough. Let me know if this is of high priority |
Thanks for the reply, @manthanguptaa. I would say it's a higher priority than the other linter task we're working on :) |
What would you like to be added?
We recently enabled periodic integration tests for 1 CPU in prow (kubernetes/test-infra#33894 / #18976 (comment)). After seeing them running for the last week (https://testgrid.k8s.io/sig-etcd-periodics), we should also enable 2 CPU and 4 CPU jobs.
As a reference, take a look at the pull request: https://github.com/kubernetes/test-infra/pull/33894/files
The current definitions for the presubmit jobs for 2 and 4 CPUs are here:
The periodic job definition is very similar. However, we need the following changes:
always_run
andbranches
, i.e.,interval
set to 24h andextra_refs
, i.e.NOTE that this pull request should be opened in the kuberentes/test-infra repository, and it should modify the
config/jobs/etcd/etcd-periodics.yaml
file.Why is this needed?
To improve test stance and help identify flaky tests.
The text was updated successfully, but these errors were encountered: