-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Divide KCPUpgrade E2E test suite #4683
🌱 Divide KCPUpgrade E2E test suite #4683
Conversation
Hi @tcordeu. Thanks for your PR. I'm waiting for a kubernetes-sigs 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/test-infra repository. |
This looks good to me |
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that currently KCPUpgradeSpec has three test specs (It
predicates) which are equal except for the flavor and the number of control plane machines, I suggest a different approach.
- Let's have KCPUpgradeSpec with a single
It
predicate but accepting in input flavor and the number of control plane machines - Let's define there Suites (
Describe
predicates) in /Users/fpandini/go/src/sigs.k8s.io/cluster-api/test/e2e/kcp_upgrade_test.go, with different combinations of flavors and number of control plane machines.
This has two benefits
- We are removing/avoiding duplication of code.
- We will get 3 test suites running in parallel (instead of two, one of them with two test specs)
71a789e
to
7f964bb
Compare
@fabriziopandini I implemented the changes you proposed, please give it a look when you're free! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice! thanks for updating the PR!
/lgtm
/test pull-cluster-api-test-full-main |
@fabriziopandini: The specified target(s) for
Use
In response to this:
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/test-infra repository. |
/test pull-cluster-api-e2e-full-main |
7f964bb
to
75a9712
Compare
Fixed! My bad |
@fabriziopandini can you force a retest? PD: For the future, can I force it? |
/test pull-cluster-api-test-main |
I will trigger e2e after unit tests pass. |
/test pull-cluster-api-e2e-full-main You need to be a reviewer to trigger the tests IIRC. |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Separate KCP scale in rollout test to improve test parallelization.
Which issue(s) this PR fixes:
Fixes #4672