Skip to content

[release-4.20] NO-ISSUE: bulk backport tests changes from main#5548

Merged
openshift-merge-bot[bot] merged 14 commits intoopenshift:release-4.20from
agullon:backport-4.20-batch
Oct 6, 2025
Merged

[release-4.20] NO-ISSUE: bulk backport tests changes from main#5548
openshift-merge-bot[bot] merged 14 commits intoopenshift:release-4.20from
agullon:backport-4.20-batch

Conversation

@agullon
Copy link
Contributor

@agullon agullon commented Oct 2, 2025

Cherry-picked all commits from the following PRs in order:
- PR #5386 - Added new releases scenario for optional, osconfig and tuned (USHIFT-6155)
- PR #5537 - Fixed XML result handling
- PR #5518 - Ginkgo test improvements and timeouts
- PR #5505 - Re-enabled router test
- PR #5528 - Fix brew dependency in image blueprints
- PR #5485 - Fix releases tests unavailable images

USHIFT-6071: Add RF Test Suites: optional, osconfig and tuned into release scenarios
(cherry picked from commit 359a6bc)
USHIFT-6183: Fix ginkgo junit results
(cherry picked from commit 3e4d0b8)
USHIFT-6175: Ginkgo releases tests are failing in CI
(cherry picked from commit 527f77d)
USHIFT-6085: reenable router RF test after 4.20 RC is available
(cherry picked from commit c6d8933)
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 2, 2025
@openshift-ci openshift-ci bot requested review from jerpeter1 and jogeo October 2, 2025 15:40
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 2, 2025
@agullon agullon closed this Oct 2, 2025
@agullon agullon reopened this Oct 2, 2025
@agullon agullon changed the base branch from main to release-4.20 October 2, 2025 15:46
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 2, 2025
@agullon agullon changed the title backport changes: WIP NO-ISSUE: bulk backport changes into release-4.20 Oct 2, 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 Oct 2, 2025
@openshift-ci-robot
Copy link

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

Details

In response to this:

Cherry-picked all commits from the following PRs in order:

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.

@pacevedom
Copy link
Contributor

/retitle [release-4.20] NO-ISSUE: bulk backport tests changes from main

@openshift-ci openshift-ci bot changed the title NO-ISSUE: bulk backport changes into release-4.20 [release-4.20] NO-ISSUE: bulk backport tests changes from main Oct 3, 2025
@agullon
Copy link
Contributor Author

agullon commented Oct 3, 2025

/test e2e-aws-tests-cache-arm e2e-aws-tests-cache

@agullon
Copy link
Contributor Author

agullon commented Oct 3, 2025

/retest

2 similar comments
@agullon
Copy link
Contributor Author

agullon commented Oct 3, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Oct 3, 2025

/retest

@agullon
Copy link
Contributor Author

agullon commented Oct 3, 2025

/test e2e-aws-tests-release e2e-aws-tests-release-arm e2e-aws-tests-bootc-release-arm e2e-aws-tests-bootc-release

@agullon
Copy link
Contributor Author

agullon commented Oct 3, 2025

/retest


AWS_BUCKET_NAME="${AWS_BUCKET_NAME:-microshift-build-cache}"
#AWS_BUCKET_NAME="${AWS_BUCKET_NAME:-microshift-build-cache}"
AWS_BUCKET_NAME="microshift-pr-5548-cache-us-west-2"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leftover?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, I'll remove this right now, this is a temp change to use a separate cache bucket
removed in 44ff054 commit

@pacevedom
Copy link
Contributor

/test e2e-aws-tests-arm

@agullon
Copy link
Contributor Author

agullon commented Oct 6, 2025

/test e2e-aws-tests-cache-arm e2e-aws-tests-cache

@agullon
Copy link
Contributor Author

agullon commented Oct 6, 2025

/test e2e-aws-tests e2e-aws-tests-arm e2e-aws-tests-bootc e2e-aws-tests-bootc-arm e2e-aws-tests-periodic e2e-aws-tests-periodic-arm e2e-aws-tests-bootc-periodic-arm e2e-aws-tests-bootc-periodic e2e-aws-tests-bootc-release-arm e2e-aws-tests-bootc-release e2e-aws-tests-release-arm e2e-aws-tests-release

@agullon
Copy link
Contributor Author

agullon commented Oct 6, 2025

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 6, 2025

@agullon: all tests passed!

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.

Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/label jira/valid-bug

@openshift-ci openshift-ci bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 6, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 6, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@pacevedom
Copy link
Contributor

/label backport-risk-assessed

@pacevedom
Copy link
Contributor

/verified by CI

@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

@pacevedom: This PR has been marked as verified by CI.

Details

In response to this:

/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 the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 6, 2025
@jerpeter1
Copy link
Member

/label staff-eng-approved

@openshift-ci openshift-ci bot added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Oct 6, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit b13b36a into openshift:release-4.20 Oct 6, 2025
19 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. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants