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 running cpu-mgr-multiNUMA e2e tests with Topology manager #88566
Enable running cpu-mgr-multiNUMA e2e tests with Topology manager #88566
Conversation
Hi @Deepthidharwar. 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/test-infra repository. |
@vpickard @ConnorDoyle , @fromanirh , Please do review and if it looks ok, need ok-to-test. |
/test pull-kubernetes-node-kubelet-serial-cpu-manager |
@Deepthidharwar: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
/ok-to-test |
1 similar comment
/ok-to-test |
/test pull-kubernetes-node-e2e-containerd |
It looks like this test is failing consistently across the board. I have posted a message on #sig-testing to see if the test env needs some tidying up. For reference, here is a link to this job run history: And here is the failure:
|
/retest |
6ed8596
to
ebb3bdc
Compare
/test pull-kubernetes-node-kubelet-serial-cpu-manager |
/test pull-kubernetes-node-kubelet-serial-topology-manager |
Failing test is not cpu-manager's test but SR-IOV device plugin tests. Looking into this. |
It's a bug I introduced in the tests which triggers when the tests are run on a box without any SRIOV device. The logic which tries to detect if we need to skip the tests for this very reason is flawed. |
@fromanirh , SRIOV detection logic is reporting error on systems that does not have one enabled https://github.com/kubernetes/kubernetes/blob/master/test/e2e_node/topology_manager_test.go#L172 . This should not error out. |
Correct. It should read like
The code as it is is correct in the flow the tests I added are using. Changing like I wrote above make it work in the general flow. |
#88721 has the fix for this as discussed above. |
The changes made as part of this patch runs fine on systems with fix in #88721. |
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 assuming the inline comment is handled
e2eskipper.Skipf("Skipping CPU Manager tests since the CPU capacity < 2") | ||
} | ||
ginkgo.By("by deleting the pods and waiting for container removal") | ||
deletePods(f, []string{pod.Name}) |
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.
If I'm not mistaken, the original code had
waitForContainerRemoval(pod.Spec.Containers[0].Name, pod.Name, pod.Namespace)
here. If so, I'd add it again.
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.
Good catch.
…er-e2e-testsuite. Signed-off-by: Deepthi Dharwar <ddharwar@redhat.com>
Signed-off-by: Deepthi Dharwar <ddharwar@redhat.com>
ebb3bdc
to
1ede096
Compare
/retest |
lgtm now. Thanks for the updates! |
/lgtm |
the refactoring was clean. thanks for the follow-up. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Deepthidharwar, derekwaynecarr 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 |
/kind cleanup |
/retest |
1 similar comment
/retest |
@Deepthidharwar: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
/test pull-kubernetes-e2e-gce |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Currently, TopologyManager e2e tests have a copy of CPU Manager e2e test code and does not support MultiNUMA support. This PR addresses both these issues by code-refactor and re-use.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: