Skip to content

Conversation

@shajmakh
Copy link
Contributor

Add basic e2e tests that checks the default behavior of performance-profile with default enabled ExecCPUAffinity: first.

@openshift-ci openshift-ci bot requested review from MarSik and swatisehgal November 13, 2025 13:46
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 13, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: shajmakh
Once this PR has been reviewed and has the lgtm label, please assign ffromani for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@shajmakh
Copy link
Contributor Author

depend on #1426

@shajmakh shajmakh force-pushed the exec-affinity-pp-e2e branch 3 times, most recently from 6ef4f1a to beeea3d Compare November 18, 2025 10:34
For High-performance configuration, cri-o started supporting exec-cpu-affinity
feature and when configured to `first` it provides the ability for exec
process to be pinned to the first CPU from the shared-CPUs IF set
or to the first one from the islolated set.
(see cri-o/cri-o@4dd7fb9)

In performance profile, we want to enable this high-performance feature
by default, and disbale it (legacy) it provides an annotation option.

The annotation is there just as a backup in case of bugs getting
reported by the consequences of this feature enablement, and should be
removed in 2 releases.

Run `./hack/render-sync.sh` to update the (no-cluster) e2e tests
expected outputs.

Signed-off-by: Shereen Haj <[email protected]>
u/s CI stops the run after 2 failures of the same test, which prevents a
full run of the tests. The fail-fast option is better be removed in test
runs that do not involve node reboots, that way the CI would reflect a
full run of the suite which would help us save reruns to see the next
failing test. In other words, removing it will reflect all of the
failing tests in one run.

remove this flag initially for suites of PP that are known to not have
reboots.

Signed-off-by: Shereen Haj <[email protected]>
Add main e2e tests that checks the behavior of
performance-profile with `ExecCPUAffinity: first` and without it.

Signed-off-by: Shereen Haj <[email protected]>
Add unit tests for functions in resources helper package for tests.

Assisted-by: Cursor v1.2.2
AI-Attribution: AIA Entirely AI, Human-initiated, Reviewed, Cursor v1.2.2 v1.0

Signed-off-by: Shereen Haj <[email protected]>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

@shajmakh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/lint beeea3d link true /test lint
ci/prow/e2e-upgrade beeea3d link true /test e2e-upgrade
ci/prow/e2e-gcp-pao-updating-profile beeea3d link true /test e2e-gcp-pao-updating-profile
ci/prow/e2e-gcp-pao beeea3d link true /test e2e-gcp-pao
ci/prow/e2e-hypershift-pao beeea3d link true /test e2e-hypershift-pao

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-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant