Skip to content
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.

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

Ibm power #56876

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Ibm power #56876

wants to merge 2 commits into from

Conversation

paigerube14
Copy link
Contributor

Reliant on these 2 pr's going in first:

@paigerube14
Copy link
Contributor Author

/work-in-progress

Copy link
Contributor

openshift-ci bot commented Sep 18, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: paigerube14

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 18, 2024
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 19, 2024
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 19, 2024
@openshift-bot
Copy link
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 24, 2024
@paigerube14
Copy link
Contributor Author

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 24, 2024
Auto User added 2 commits November 14, 2024 14:52
rh-pre-commit.version: 2.2.0
rh-pre-commit.check-secrets: ENABLED
rh-pre-commit.version: 2.2.0
rh-pre-commit.check-secrets: ENABLED
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@paigerube14: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-redhat-chaos-prow-scripts-main-4.17-nightly-krkn-hub-ibm-cloud-node-tests redhat-chaos/prow-scripts presubmit Presubmit changed
pull-ci-redhat-chaos-prow-scripts-main-4.16-nightly-krkn-hub-tests-416-azure-node redhat-chaos/prow-scripts presubmit Registry content changed
periodic-ci-redhat-chaos-prow-scripts-main-4.18-nightly-krkn-hub-node-tests-compact N/A periodic Registry content changed
periodic-ci-redhat-chaos-prow-scripts-main-4.17-nightly-krkn-hub-cloud-gcp-node-tests N/A periodic Registry content changed
periodic-ci-redhat-chaos-prow-scripts-main-4.15-nightly-krkn-hub-node-tests-415 N/A periodic Registry content changed
periodic-ci-redhat-chaos-prow-scripts-main-4.17-nightly-krkn-hub-node-tests N/A periodic Registry content changed
periodic-ci-redhat-chaos-prow-scripts-main-4.17-nightly-krkn-hub-tests-417-azure-node N/A periodic Registry content changed
periodic-ci-redhat-chaos-prow-scripts-main-4.18-nightly-krkn-hub-node-tests N/A periodic Registry content changed
periodic-ci-redhat-chaos-prow-scripts-main-rosa-4.17-nightly-krkn-rosa-hcp-node N/A periodic Registry content changed
periodic-ci-redhat-chaos-prow-scripts-main-4.16-nightly-krkn-hub-node-tests N/A periodic Registry content changed
periodic-ci-redhat-chaos-prow-scripts-main-4.16-nightly-krkn-hub-cloud-gcp-node-tests N/A periodic Registry content changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@paigerube14
Copy link
Contributor Author

/pj-rehearse pull-ci-redhat-chaos-prow-scripts-main-4.17-nightly-krkn-hub-ibm-cloud-node-tests

@openshift-ci-robot
Copy link
Contributor

@paigerube14: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

Copy link
Contributor

openshift-ci bot commented Nov 15, 2024

@paigerube14: 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/rehearse/redhat-chaos/prow-scripts/main/4.17-nightly-krkn-hub-ibm-cloud-node-tests ef1570c link unknown /pj-rehearse pull-ci-redhat-chaos-prow-scripts-main-4.17-nightly-krkn-hub-ibm-cloud-node-tests
ci/prow/generated-config ef1570c link true /test generated-config

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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants