[release-4.4] fix guaranteed and cpu affinity tests #140
Conversation
in guaranteed mode, pod can land on any NOT reserved cpu (not just isolated one) Signed-off-by: Yuval Kashtan <yuvalkashtan@gmail.com>
String comparison is not good enough, since reservation might be obaied with "," and/or "-", in a different format than that is returned from taskset. Reverted to using cpusets comparison Signed-off-by: Yuval Kashtan <yuvalkashtan@gmail.com>
|
@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request. 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. |
openshift-ci-robot
added
the
needs-ok-to-test
|
Hi @openshift-cherrypick-robot. Thanks for your PR. I'm waiting for a openshift-kni 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. |
|
/ok-to-test |
openshift-ci-robot
added
ok-to-test
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: openshift-cherrypick-robot, slintes 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 |
openshift-ci-robot
added
the
approved
This is an automated cherry-pick of #138
/assign yanirq