-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Create separate configuration for extended integration tests. #34708
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
base: master
Are you sure you want to change the base?
Create separate configuration for extended integration tests. #34708
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mbobrovskyi The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @mbobrovskyi. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/hold for kubernetes-sigs/kueue#5068. |
45209ae
to
8302e02
Compare
8302e02
to
0766c2b
Compare
/ok-to-test
@mbobrovskyi is it ready now? |
Create separate configuration for extended integration tests.
Sometimes we miss testing the slow and redundant integration tests before merging to main, which results in errors in periodic tests. This happens because the presubmit integration tests are filtered by the
INTEGRATION_RUN_ALL
flag.To prevent this, I propose running the extended tests in parallel with the required tests instead of skipping it in presubmit tests. As for the multikueue integration tests, we can run all of them – they only take 6m24s.