Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #1374

/assign mrniranjan

Skip test case checking if stalld is setting
sched_fifo scheduling algorithm due to
known issue https://issues.redhat.com/browse/RHEL-108827

Signed-off-by: Niranjan M.R <[email protected]>
@jmencak
Copy link
Contributor

jmencak commented Aug 28, 2025

/approve
/lgtm

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

openshift-ci bot commented Aug 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmencak, openshift-cherrypick-robot

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 Aug 28, 2025
@mrniranjan
Copy link
Contributor

/title OCPBUGS-61052: [release-4.19] NO-JIRA: E2E: skip stalld test case checking sched_fifo

@mrniranjan
Copy link
Contributor

/retitle: OCPBUGS-61052: [release-4.19] NO-JIRA: E2E: skip stalld test case checking sched_fifo

@openshift-ci openshift-ci bot changed the title [release-4.19] NO-JIRA: E2E: skip stalld test case checking sched_fifo : OCPBUGS-61052: [release-4.19] NO-JIRA: E2E: skip stalld test case checking sched_fifo Aug 29, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 29, 2025
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-61052, 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.19.z) matches configured target version for branch (4.19.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-61051 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-61051 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
  • bug has dependents

Requesting review from QA contact:
/cc @mrniranjan

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

In response to this:

This is an automated cherry-pick of #1374

/assign mrniranjan

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 a review from mrniranjan August 29, 2025 13:30
@mrniranjan
Copy link
Contributor

/retitle OCPBUGS-61052: [release-4.19] NO-JIRA: E2E: skip stalld test case checking sched_fifo

@openshift-ci openshift-ci bot changed the title : OCPBUGS-61052: [release-4.19] NO-JIRA: E2E: skip stalld test case checking sched_fifo OCPBUGS-61052: [release-4.19] NO-JIRA: E2E: skip stalld test case checking sched_fifo Aug 29, 2025
@mrniranjan
Copy link
Contributor

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 29, 2025

@openshift-cherrypick-robot: 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 Aug 31, 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 Aug 31, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 3671b8d into openshift:release-4.19 Aug 31, 2025
19 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-61052: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-61052 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #1374

/assign mrniranjan

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

/cherry-pick release-4.18

@openshift-cherrypick-robot
Copy link
Author

@rshemtov13: new pull request created: #1387

In response to this:

/cherry-pick release-4.18

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.

@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.19.0-202508311138.p0.g3671b8d.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

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

Development

Successfully merging this pull request may close these issues.

7 participants