Skip to content

Conversation

pmtk
Copy link
Member

@pmtk pmtk commented May 19, 2025

No description provided.

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

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

In response to this:

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.

@pmtk
Copy link
Member Author

pmtk commented May 19, 2025

/test ?

Copy link
Contributor

openshift-ci bot commented May 19, 2025

@pmtk: The following commands are available to trigger required jobs:

/test e2e-aws-ai-model-serving
/test e2e-aws-footprint-and-performance
/test e2e-aws-tests
/test e2e-aws-tests-arm
/test e2e-aws-tests-bootc
/test e2e-aws-tests-bootc-arm
/test e2e-aws-tests-bootc-periodic
/test e2e-aws-tests-bootc-periodic-arm
/test e2e-aws-tests-cache
/test e2e-aws-tests-cache-arm
/test e2e-aws-tests-periodic
/test e2e-aws-tests-periodic-arm
/test images
/test ocp-full-conformance-rhel-eus
/test ocp-full-conformance-serial-rhel-eus
/test test-rpm
/test test-unit
/test verify

The following commands are available to trigger optional jobs:

/test security
/test test-rebase

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-microshift-release-4.19-e2e-aws-tests
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-arm
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-bootc
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-bootc-arm
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-bootc-periodic
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-bootc-periodic-arm
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-periodic
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-periodic-arm
pull-ci-openshift-microshift-release-4.19-images
pull-ci-openshift-microshift-release-4.19-security
pull-ci-openshift-microshift-release-4.19-test-unit
pull-ci-openshift-microshift-release-4.19-verify

In response to this:

/test ?

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.

@pmtk
Copy link
Member Author

pmtk commented May 19, 2025

/test e2e-aws-tests-bootc-periodic

@openshift-ci openshift-ci bot requested review from ggiguash and jerpeter1 May 19, 2025 15:00
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 19, 2025
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

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 19, 2025
@pmtk pmtk changed the title NO-ISSUE: Update common_versions.sh -> RC [release-4.19] NO-ISSUE: Update common_versions.sh -> RC May 19, 2025
@eslutsky
Copy link
Contributor

/test e2e-aws-tests-bootc

@eslutsky
Copy link
Contributor

/test e2e-aws-tests-bootc-periodic

@pmtk pmtk force-pushed the 4.19/common-versions/rc branch from f6a69a8 to 31a8796 Compare May 20, 2025 06:33
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label May 20, 2025
@pmtk
Copy link
Member Author

pmtk commented May 20, 2025

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

@pacevedom
Copy link
Contributor

/retest

@pacevedom
Copy link
Contributor

/label cherry-pick-approved
/label backport-risk-assessed

@openshift-ci openshift-ci bot added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels May 20, 2025
@ggiguash
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 21, 2025
@pacevedom
Copy link
Contributor

/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 May 21, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a8a62f3 and 2 for PR HEAD 31a8796 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b55372b and 1 for PR HEAD 31a8796 in total

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label May 21, 2025
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

@pmtk pmtk force-pushed the 4.19/common-versions/rc branch from cb8dea4 to fcae28d Compare May 21, 2025 11:09
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 21, 2025
@pmtk pmtk force-pushed the 4.19/common-versions/rc branch from fcae28d to 61373ed Compare May 21, 2025 12:29
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label May 21, 2025
@pmtk pmtk force-pushed the 4.19/common-versions/rc branch from 61373ed to e73c14c Compare May 21, 2025 13:55
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

@pmtk
Copy link
Member Author

pmtk commented May 21, 2025

/override ci/prow/e2e-aws-tests-bootc-periodic ci/prow/e2e-aws-tests-bootc

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 21, 2025
Copy link
Contributor

openshift-ci bot commented May 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pacevedom, pmtk

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:
  • OWNERS [ggiguash,pacevedom,pmtk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

openshift-ci bot commented May 21, 2025

@pmtk: Overrode contexts on behalf of pmtk: ci/prow/e2e-aws-tests-bootc, ci/prow/e2e-aws-tests-bootc-periodic

In response to this:

/override ci/prow/e2e-aws-tests-bootc-periodic ci/prow/e2e-aws-tests-bootc

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.

Copy link
Contributor

openshift-ci bot commented May 21, 2025

@pmtk: 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-periodic e73c14c link true /test e2e-aws-tests-bootc-periodic
ci/prow/e2e-aws-tests-bootc e73c14c link true /test e2e-aws-tests-bootc

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 10baa83 into openshift:release-4.19 May 21, 2025
13 checks passed
@pmtk pmtk deleted the 4.19/common-versions/rc branch May 21, 2025 16:06
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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants