Skip to content

rebase-4.13.0-0.nightly-2023-06-20-224158_amd64-2023-06-20_arm64-2023-06-23#1960

Merged
openshift-merge-robot merged 5 commits intorelease-4.13from
rebase-4.13.0-0.nightly-2023-06-20-224158_amd64-2023-06-20_arm64-2023-06-23
Jun 26, 2023
Merged

rebase-4.13.0-0.nightly-2023-06-20-224158_amd64-2023-06-20_arm64-2023-06-23#1960
openshift-merge-robot merged 5 commits intorelease-4.13from
rebase-4.13.0-0.nightly-2023-06-20-224158_amd64-2023-06-20_arm64-2023-06-23

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

amd64: 4.13.0-0.nightly-2023-06-20-224158
arm64: 4.13.0-0.nightly-arm64-2023-06-23-125055
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.13-rebase-on-nightlies/1673194442686730240

/label tide/merge-method-squash

@openshift-ci openshift-ci Bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jun 26, 2023
@openshift-ci openshift-ci Bot requested review from copejon and stlaz June 26, 2023 05:11
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 26, 2023

@microshift-rebase-script[bot]: 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-openshift-conformance-reduced-arm 79fa1d7 link false /test e2e-openshift-conformance-reduced-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/test-infra repository. I understand the commands that are listed here.

@dhellmann
Copy link
Copy Markdown
Contributor

/lgtm
/label backport-risk-assessed
/label jira/valid-bug

@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 Jun 26, 2023
@dhellmann
Copy link
Copy Markdown
Contributor

/approve

@dhellmann dhellmann added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 26, 2023
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 26, 2023
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 26, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhellmann, microshift-rebase-script[bot]

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 Jun 26, 2023
@openshift-merge-robot openshift-merge-robot merged commit 512369a into release-4.13 Jun 26, 2023
@openshift-merge-robot openshift-merge-robot deleted the rebase-4.13.0-0.nightly-2023-06-20-224158_amd64-2023-06-20_arm64-2023-06-23 branch June 26, 2023 18:33
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. lgtm Indicates that a PR is ready to be merged. 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