Skip to content

[release-4.20] USHIFT-6155: Add RF Test Suites: optional, osconfig and tuned into release scenarios#5506

Closed
agullon wants to merge 2 commits intoopenshift:release-4.20from
agullon:USHIFT-6155
Closed

[release-4.20] USHIFT-6155: Add RF Test Suites: optional, osconfig and tuned into release scenarios#5506
agullon wants to merge 2 commits intoopenshift:release-4.20from
agullon:USHIFT-6155

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Sep 22, 2025

This is a manual cherrypick from #5386 PR

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 22, 2025
@agullon agullon changed the title [release-4.20] Add RF Test Suites: optional, osconfig and tuned into release scenarios [release-4.20] USHIFT-6155: Add RF Test Suites: optional, osconfig and tuned into release scenarios Sep 22, 2025
@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 22, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 22, 2025

@agullon: This pull request references USHIFT-6155 which is a valid jira issue.

Details

In response to this:

This is a manual cherrypick from #5386 PR

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 Sep 22, 2025

/test e2e-aws-tests-cache-arm

@agullon
Copy link
Contributor Author

agullon commented Sep 22, 2025

/test e2e-aws-tests-cache

@agullon
Copy link
Contributor Author

agullon commented Sep 23, 2025

/retest

1 similar comment
@agullon
Copy link
Contributor Author

agullon commented Sep 24, 2025

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 24, 2025

@agullon: 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-aws-tests-bootc-release-arm 351e79e link true /test e2e-aws-tests-bootc-release-arm
ci/prow/e2e-aws-tests-release-arm 351e79e link true /test e2e-aws-tests-release-arm
ci/prow/e2e-aws-tests-bootc-release 351e79e link true /test e2e-aws-tests-bootc-release
ci/prow/e2e-aws-tests-release 351e79e link true /test e2e-aws-tests-release

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

PR needs rebase.

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.

@agullon agullon closed this Oct 3, 2025
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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants