Skip to content

no-merge: validate pr #2293

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

Open
wants to merge 1 commit into
base: release-4.18
Choose a base branch
from

Conversation

eggfoobar
Copy link

this should not be merged into 4.18, only validating for customer usecase as a custom payload

/hold

this should not be merged into 4.18, only validating for customer usecase as a custom payload

Signed-off-by: ehila <[email protected]>
@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label May 9, 2025
@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 9, 2025
@openshift-ci-robot
Copy link

@eggfoobar: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot requested review from bertinatto and p0lyn0mial May 9, 2025 14:38
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label May 9, 2025
Copy link

openshift-ci bot commented May 9, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: eggfoobar
Once this PR has been reviewed and has the lgtm label, please assign p0lyn0mial 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

Copy link

openshift-ci bot commented May 9, 2025

@eggfoobar: 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/okd-scos-e2e-aws-ovn 9d1921e link false /test okd-scos-e2e-aws-ovn
ci/prow/verify-commits 9d1921e link true /test verify-commits
ci/prow/e2e-aws-ovn-serial 9d1921e link true /test e2e-aws-ovn-serial
ci/prow/e2e-aws-crun-wasm 9d1921e link true /test e2e-aws-crun-wasm
ci/prow/e2e-gcp-ovn-upgrade 9d1921e link true /test e2e-gcp-ovn-upgrade
ci/prow/e2e-aws-ovn-cgroupsv2 9d1921e link true /test e2e-aws-ovn-cgroupsv2

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
backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants