Skip to content

OCPBUGS-58346: [release-4.18] [manual] e2e: arm: Add arm kernelPageSize e2e testing suite #1355

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jul 8, 2025
Merged

OCPBUGS-58346: [release-4.18] [manual] e2e: arm: Add arm kernelPageSize e2e testing suite #1355

merged 1 commit into from
Jul 8, 2025

Conversation

rshemtov13
Copy link
Contributor

Manual backport of #1307 combined with #1330 to backport e2e tests for kernelPageSize on arm

@rshemtov13
e2e: arm: Add arm kernelPageSize e2e testing suite
dc9868c 
Manual backport of openshift#1307 combined with openshift#1330 to backport e2e tests for kernelPageSize on arm

Signed-off-by: Roy Shemtov <[email protected]>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 3, 2025
@openshift-ci-robot
Copy link
Contributor

@rshemtov13: This pull request references Jira Issue OCPBUGS-58346, which is invalid:

  • expected Jira Issue OCPBUGS-58346 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Manual backport of #1307 combined with #1330 to backport e2e tests for kernelPageSize on arm

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.

@openshift-ci openshift-ci bot requested review from jmencak and MarSik July 3, 2025 10:57
@rshemtov13
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@rshemtov13: This pull request references Jira Issue OCPBUGS-58346, which is invalid:

  • expected Jira Issue OCPBUGS-58346 to depend on a bug targeting a version in 4.19.0, 4.19.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

@rshemtov13
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 3, 2025
@openshift-ci-robot
Copy link
Contributor

@rshemtov13: This pull request references Jira Issue OCPBUGS-58346, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-58350 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-58350 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @rshemtov13

In response to this:

/jira refresh

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.

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jul 3, 2025

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: rshemtov13.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@rshemtov13: This pull request references Jira Issue OCPBUGS-58346, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-58350 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-58350 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
  • bug has dependents

Requesting review from QA contact:
/cc @rshemtov13

In response to this:

/jira refresh

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.

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.

@jmencak
Copy link
Contributor

jmencak commented Jul 3, 2025

Thank you for the PR.
/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 3, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jul 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmencak, rshemtov13

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 3, 2025
@rshemtov13
Copy link
Contributor Author

/retest-required

@ffromani
Copy link
Contributor

ffromani commented Jul 5, 2025

/test okd-scos-e2e-aws-ovn

@mrniranjan
Copy link
Contributor

/retest-required

@mrniranjan
Copy link
Contributor

/test okd-scos-e2e-aws-ovn

2 similar comments
@rshemtov13
Copy link
Contributor Author

/test okd-scos-e2e-aws-ovn

@rshemtov13
Copy link
Contributor Author

/test okd-scos-e2e-aws-ovn

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jul 7, 2025

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

@yanirq
Copy link
Contributor

yanirq commented Jul 8, 2025

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jul 8, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 5932024 into openshift:release-4.18 Jul 8, 2025
17 checks passed
@openshift-ci-robot
Copy link
Contributor

@rshemtov13: Jira Issue OCPBUGS-58346 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state.

In response to this:

Manual backport of #1307 combined with #1330 to backport e2e tests for kernelPageSize on arm

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.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: cluster-node-tuning-operator
This PR has been included in build cluster-node-tuning-operator-container-v4.18.0-202507081733.p0.g5932024.assembly.stream.el9.
All builds following this will include this PR.

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

@jmencak jmencak Awaiting requested review from jmencak

@MarSik MarSik Awaiting requested review from MarSik

Assignees

@jmencak jmencak

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
7 participants
@rshemtov13 @openshift-ci-robot @jmencak @ffromani @mrniranjan @yanirq @openshift-bot