Skip to content

NO-ISSUE: rebase-release-4.16-4.16.0-0.nightly-2024-08-20-170018_amd64-2024-08-20_arm64-2024-08-20#3797

Closed
microshift-rebase-script[bot] wants to merge 4 commits intorelease-4.16from
rebase-release-4.16-4.16.0-0.nightly-2024-08-20-170018_amd64-2024-08-20_arm64-2024-08-20
Closed

NO-ISSUE: rebase-release-4.16-4.16.0-0.nightly-2024-08-20-170018_amd64-2024-08-20_arm64-2024-08-20#3797
microshift-rebase-script[bot] wants to merge 4 commits intorelease-4.16from
rebase-release-4.16-4.16.0-0.nightly-2024-08-20-170018_amd64-2024-08-20_arm64-2024-08-20

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.16.0-0.nightly-2024-08-20-170018
arm64: 4.16.0-0.nightly-arm64-2024-08-20-193052
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.16-rebase-on-nightlies/1826107244018667520

/label tide/merge-method-squash
/label cherry-pick-approved
/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 21, 2024
@openshift-ci-robot
Copy link
Copy Markdown

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

amd64: 4.16.0-0.nightly-2024-08-20-170018
arm64: 4.16.0-0.nightly-arm64-2024-08-20-193052
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.16-rebase-on-nightlies/1826107244018667520

/label tide/merge-method-squash
/label cherry-pick-approved
/label backport-risk-assessed
/label jira/valid-bug

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 tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. 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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 21, 2024
@openshift-ci openshift-ci Bot requested review from ggiguash and pliurh August 21, 2024 04:26
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 21, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: microshift-rebase-script[bot]
Once this PR has been reviewed and has the lgtm label, please assign zshi-redhat for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 21, 2024

@microshift-rebase-script[bot]: 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/ocp-conformance-rhel-eus 8235172 link true /test ocp-conformance-rhel-eus
ci/prow/microshift-metal-tests-arm 8235172 link true /test microshift-metal-tests-arm
ci/prow/microshift-metal-tests 8235172 link true /test microshift-metal-tests
ci/prow/ocp-conformance-rhel-eus-arm 8235172 link true /test ocp-conformance-rhel-eus-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.

@copejon
Copy link
Copy Markdown
Contributor

copejon commented Aug 21, 2024

Closing with the same reason as #3798 (comment)

/close

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Aug 21, 2024

@copejon: Closed this PR.

Details

In response to this:

Closing with the same reason as #3798 (comment)

/close

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 openshift-ci Bot closed this Aug 21, 2024
@microshift-rebase-script microshift-rebase-script Bot deleted the rebase-release-4.16-4.16.0-0.nightly-2024-08-20-170018_amd64-2024-08-20_arm64-2024-08-20 branch August 22, 2024 04:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants