Skip to content

Conversation

prb112
Copy link

@prb112 prb112 commented Sep 7, 2025

Adds operatorframework.io/arch.ppc64le supported flag.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 7, 2025
@openshift-ci-robot
Copy link

@prb112: This pull request references MULTIARCH-5554 which is a valid jira issue.

In response to this:

Adds operatorframework.io/arch.ppc64le supported flag.

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 gnufied and stephenfin September 7, 2025 00:37
@jsafrane
Copy link
Contributor

jsafrane commented Sep 9, 2025

/lgtm
/approve

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

openshift-ci bot commented Sep 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, prb112

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 Sep 9, 2025
@jsafrane
Copy link
Contributor

jsafrane commented Sep 9, 2025

@prb112 can your QE add verified label or at least add a comment that they verified it?

@prb112
Copy link
Author

prb112 commented Sep 9, 2025

Hey @jsafrane sure - can do. Thanks, Paul

@Jeevaann
Copy link

Jeevaann commented Oct 6, 2025

/verified

@openshift-ci-robot
Copy link

@Jeevaann: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

In response to this:

/verified

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.

@prb112
Copy link
Author

prb112 commented Oct 6, 2025

/verified by IBM Power QE

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 6, 2025
@openshift-ci-robot
Copy link

@prb112: This PR has been marked as verified by IBM Power QE.

In response to this:

/verified by IBM Power QE

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.

@prb112
Copy link
Author

prb112 commented Oct 6, 2025

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 12ef6e8 and 2 for PR HEAD a180d47 in total

@prb112
Copy link
Author

prb112 commented Oct 7, 2025

/retest-required

2 similar comments
@prb112
Copy link
Author

prb112 commented Oct 7, 2025

/retest-required

@prb112
Copy link
Author

prb112 commented Oct 7, 2025

/retest-required

Copy link
Contributor

openshift-ci bot commented Oct 8, 2025

@prb112: 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/e2e-azure-csi a180d47 link true /test e2e-azure-csi
ci/prow/e2e-azure-file-nfs-csi a180d47 link true /test e2e-azure-file-nfs-csi

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
approved Indicates a PR has been approved by an approver from all required OWNERS files. 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. verified Signifies that the PR passed pre-merge verification criteria
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants