-
Notifications
You must be signed in to change notification settings - Fork 90
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
Consolidate parallel and sequential lanes #717
Conversation
cc @qinqon |
5ae5d75
to
4c4d12c
Compare
4c4d12c
to
cfbd4bb
Compare
Run the e2e handler test lane only once, configured to use default 50% of worker nodes to process NNCPs concurrently. For that reason, setting number of nodes to 5 so that 2 nodes run concurrently (4/2 == 2) Signed-off-by: Radim Hrazdil <[email protected]>
Now when a failing NNCP is applied, we accept NNCEs in two states: aborted and failed. Signed-off-by: Radim Hrazdil <[email protected]>
cfbd4bb
to
4e4f9c9
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qinqon 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 |
@rhrazdil: The following test failed, say
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. I understand the commands that are listed here. |
Consolidate parallel and sequential lanes
Both e2e-handler-k8s-parallel and e2e-handler-k8s lanes run the same tests with
setting maxUnavailable to 50%. After merging this PR, parallel lane can be removed.
This PR increases number of nodes to 5 so that even 50% of the worker nodes yields
2 nodes that can run in parallel.
Signed-off-by: Radim Hrazdil [email protected]
Is this a BUG FIX or a FEATURE ?:
What this PR does / why we need it:
Special notes for your reviewer:
Release note: