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

WIP: Fix uncertain device 413 #1842

Closed

Conversation

bertinatto
Copy link
Member

No description provided.

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jan 4, 2024
@bertinatto
Copy link
Member Author

/test verify

@openshift-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 4, 2024
Copy link

openshift-ci bot commented Jan 4, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@bertinatto
Copy link
Member Author

/test verify

1 similar comment
@bertinatto
Copy link
Member Author

/test verify

@bertinatto
Copy link
Member Author

/test images

@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Jan 4, 2024
Copy link

openshift-ci bot commented Jan 4, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bertinatto
Once this PR has been reviewed and has the lgtm label, please assign soltysh for approval. For more information see the Kubernetes Code Review Process.

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

@bertinatto bertinatto marked this pull request as ready for review January 4, 2024 13:01
@bertinatto bertinatto marked this pull request as draft January 4, 2024 13:02
@bertinatto
Copy link
Member Author

/test all

@bertinatto bertinatto marked this pull request as ready for review January 4, 2024 13:09
@openshift-ci-robot
Copy link

@bertinatto: the contents of this pull request could not be automatically validated.

The following commits are valid:

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot requested review from mfojtik and mrunalp January 4, 2024 13:13
@bertinatto bertinatto marked this pull request as draft January 4, 2024 13:16
@bertinatto
Copy link
Member Author

/test unit
/test verify

@bertinatto bertinatto marked this pull request as ready for review January 4, 2024 13:24
@openshift-ci openshift-ci bot requested a review from deads2k January 4, 2024 13:29
@bertinatto
Copy link
Member Author

/test all

Copy link

openshift-ci bot commented Jan 4, 2024

@bertinatto: 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-cgroupsv2 33a42bf link true /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-crun 33a42bf link true /test e2e-aws-ovn-crun

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.

@bertinatto bertinatto closed this Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants