Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TRT-1359: Ignore azure interaction errors since they are not fatal for our usage #28420

Merged

Conversation

xueqzhan
Copy link
Contributor

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 27, 2023
@xueqzhan
Copy link
Contributor Author

/retest-required

@dgoodwin
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 28, 2023
Copy link
Contributor

openshift-ci bot commented Nov 28, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, xueqzhan

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:

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

@xueqzhan xueqzhan changed the title Ignore azure interaction errors since they are not fatal for our usage TRT-1359: Ignore azure interaction errors since they are not fatal for our usage Nov 29, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 29, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 29, 2023

@xueqzhan: This pull request references TRT-1359 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.15.0" version, but no target version was set.

In response to this:

TRT-1359

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.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 639414f and 2 for PR HEAD 8963c37 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD b7a93b9 and 1 for PR HEAD 8963c37 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a95e17f and 0 for PR HEAD 8963c37 in total

Copy link
Contributor

openshift-ci bot commented Dec 1, 2023

@xueqzhan: 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-ovn-single-node-upgrade 8963c37 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node-serial 8963c37 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-gcp-csi 8963c37 link false /test e2e-gcp-csi
ci/prow/e2e-agnostic-ovn-cmd 8963c37 link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-gcp-ovn-rt-upgrade 8963c37 link false /test e2e-gcp-ovn-rt-upgrade

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/test-infra repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

/hold

Revision 8963c37 was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 1, 2023
@openshift-trt-bot
Copy link

Job Failure Risk Analysis for sha: 8963c37

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-gcp-ovn IncompleteTests
Tests for this run (99) are below the historical average (1549): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@xueqzhan
Copy link
Contributor Author

xueqzhan commented Dec 1, 2023

/retest-required

@xueqzhan
Copy link
Contributor Author

xueqzhan commented Dec 4, 2023

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 4, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD c782a30 and 2 for PR HEAD 8963c37 in total

@openshift-merge-bot openshift-merge-bot bot merged commit dbee35f into openshift:master Dec 5, 2023
17 of 22 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-tests-container-v4.15.0-202312050231.p0.gdbee35f.assembly.stream for distgit openshift-enterprise-tests.
All builds following this will include this PR.

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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants