Skip to content

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Nov 6, 2025

manual backport changes from #5637

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

@agullon: This pull request explicitly references no jira issue.

Details

In response to this:

manual backport changes from #5637

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.

@agullon
Copy link
Contributor Author

agullon commented Nov 6, 2025

/retest

@openshift-ci openshift-ci bot requested review from eslutsky and pmtk November 6, 2025 11:50
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 6, 2025
@agullon
Copy link
Contributor Author

agullon commented Nov 6, 2025

/retest

3 similar comments
@agullon
Copy link
Contributor Author

agullon commented Nov 6, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Nov 6, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Nov 6, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Nov 9, 2025

/test all

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 9, 2025
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 9, 2025
@agullon
Copy link
Contributor Author

agullon commented Nov 9, 2025

/restes

@agullon
Copy link
Contributor Author

agullon commented Nov 9, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Nov 10, 2025

/test all

@agullon
Copy link
Contributor Author

agullon commented Nov 11, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Nov 13, 2025

/retest

2 similar comments
@agullon
Copy link
Contributor Author

agullon commented Nov 14, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Nov 17, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Nov 17, 2025

/retest

2 similar comments
@agullon
Copy link
Contributor Author

agullon commented Nov 17, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Nov 17, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Nov 18, 2025

/retest

2 similar comments
@agullon
Copy link
Contributor Author

agullon commented Nov 18, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Nov 18, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Nov 18, 2025

/retest

1 similar comment
@agullon
Copy link
Contributor Author

agullon commented Nov 18, 2025

/retest

@ggiguash
Copy link
Contributor

/lgtm
/label backport-risk-assessed
/label jira/valid-bug
/verified by ci

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

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/lgtm
/label backport-risk-assessed
/label jira/valid-bug
/verified by ci

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 added 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. labels Nov 18, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 18, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, ggiguash

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@ggiguash
Copy link
Contributor

The failure is not related to changes. Overriding to make progress
/override ci/prow/e2e-aws-tests-bootc-release-arm

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 0ccad8c and 2 for PR HEAD ac6bbae in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

@ggiguash: Overrode contexts on behalf of ggiguash: ci/prow/e2e-aws-tests-bootc-release-arm

Details

In response to this:

The failure is not related to changes. Overriding to make progress
/override ci/prow/e2e-aws-tests-bootc-release-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 kubernetes-sigs/prow repository.

@ggiguash
Copy link
Contributor

/override ci/prow/e2e-aws-tests-bootc-release-arm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

@ggiguash: Overrode contexts on behalf of ggiguash: ci/prow/e2e-aws-tests-bootc-release-arm

Details

In response to this:

/override ci/prow/e2e-aws-tests-bootc-release-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 kubernetes-sigs/prow repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2025

@agullon: The following test 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-aws-tests-bootc-release-arm ac6bbae link true /test e2e-aws-tests-bootc-release-arm

Full PR test history. Your PR dashboard.

Details

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.

@openshift-merge-bot openshift-merge-bot bot merged commit bbfd724 into openshift:release-4.20 Nov 18, 2025
17 checks passed
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. 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