NO-JIRA: e2e: perf-prof: increase logging for debugging #974
Conversation
One of the tests is failing in u/s and printing out the pod events is not enough for debugging. Add another condition to skip the test if the requested cpus is greater than what the node can provide; and log a bit more info about the pod to be created. Signed-off-by: Shereen Haj <shajmakh@redhat.com>
|
/lgtm |
|
[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-required |
1 similar comment
|
/retest-required |
|
@shajmakh if this need a cherry pick - please open a bug and add to the PR title (otherwise add the NO-JIRA title) |
|
/retest-required |
|
/retitle NO-JIRA: e2e: perf-prof: increase logging for debugging |
openshift-ci
bot
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. |
|
@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-202403061047.p0.ge4995df.assembly.stream.el9 for distgit cluster-node-tuning-operator. |
One of the tests is failing in u/s and printing out the pod events is not enough for debugging. Add another condition to skip the test if the requested cpus is greater than what the node can provide; and log a bit more info about the pod to be created. Signed-off-by: Shereen Haj <shajmakh@redhat.com>
One of the tests is failing in u/s and printing out the pod events is not enough for debugging.
Add another condition to skip the test if the requested cpus is greater than what the node can provide; and log a bit more info about the pod to be created.