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

Consolidate parallel and sequential lanes #717

Merged
merged 2 commits into from
Mar 25, 2021

Conversation

rhrazdil
Copy link
Collaborator

@rhrazdil rhrazdil commented Mar 23, 2021

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 ?:

Uncomment only one, leave it on its own line:

/kind bug
/kind enhancement

What this PR does / why we need it:

Special notes for your reviewer:

Release note:

run e2e-handler tests in parallel with 50% of worker nodes

@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/enhancement dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/M labels Mar 23, 2021
@rhrazdil
Copy link
Collaborator Author

cc @qinqon

Radim Hrazdil added 2 commits March 25, 2021 13:33
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]>
@rhrazdil rhrazdil force-pushed the consolidate_lanes branch from cfbd4bb to 4e4f9c9 Compare March 25, 2021 12:34
@qinqon
Copy link
Member

qinqon commented Mar 25, 2021

/lgtm
/approve

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 25, 2021
@kubevirt-bot
Copy link
Collaborator

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 25, 2021
@kubevirt-bot
Copy link
Collaborator

@rhrazdil: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-kubernetes-nmstate-e2e-handler-k8s-future 4e4f9c9 link /test pull-kubernetes-nmstate-e2e-handler-k8s-future

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.

@kubevirt-bot kubevirt-bot merged commit d9ac731 into nmstate:master Mar 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/enhancement lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants