NO-JIRA: perfprof: e2e: account for node base load #1047
Conversation
Currently the test would fail when tested on machines with exactly isolated cpus equal to the requested cpus by the pod. This is because the worker nodes has already other pods running on them and thus they are using already a portion of the isolated cpus of the node. Scheduling a pod requesting all allocatable cpus would fail due to insufficient cpus on node. Skip the test if the testing environment is not suitable for the test's requirements. Signed-off-by: Shereen Haj <shajmakh@redhat.com>
|
blocking: openshift/release#47439 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MarSik, shajmakh 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
bot
added
the
approved
|
/retest |
shajmakh
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@shajmakh: This pull request explicitly references no jira issue. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/retest |
|
@shajmakh: all tests passed! Full PR test history. Your PR dashboard. 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. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build cluster-node-tuning-operator-container-v4.16.0-202404291018.p0.g163236c.assembly.stream.el9 for distgit cluster-node-tuning-operator. |
Currently the test would fail when tested on machines with exactly isolated cpus equal to the requested cpus by the pod. This is because the worker nodes has already other pods running on them and thus they are using already a portion of the isolated cpus of the node. Scheduling a pod requesting all allocatable cpus would fail due to insufficient cpus on node.
Skip the test if the testing environment is not suitable for the test's requirements.