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

OCPNODE-2627: enable upstream dra tests #2103

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

kannon92
Copy link

@kannon92 kannon92 commented Oct 4, 2024

What type of PR is this?

/kind feature

What this PR does / why we need it:

I want to enable e2e tests for DRA to prepare for DRA beta in 4.19.

We have a few teams interested in DRA and we want to start testing this in openshift early.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


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

openshift-ci-robot commented Oct 4, 2024

@kannon92: This pull request references OCPNODE-2627 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 spike to target the "4.18.0" version, but no target version was set.

In response to this:

What type of PR is this?

/kind feature

What this PR does / why we need it:

I want to enable e2e tests for DRA to prepare for DRA beta in 4.19.

We have a few teams interested in DRA and we want to start testing this in openshift early.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 4, 2024
@openshift-ci openshift-ci bot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 4, 2024
@openshift-ci-robot
Copy link

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

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.

Copy link

openshift-ci bot commented Oct 4, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kannon92
Once this PR has been reviewed and has the lgtm label, please assign bertinatto 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

@openshift-ci-robot
Copy link

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

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-robot
Copy link

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

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.

Copy link

openshift-ci bot commented Oct 9, 2024

@kannon92: 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-gcp 9412137 link true /test e2e-gcp
ci/prow/e2e-aws-ovn-crun 9412137 link true /test e2e-aws-ovn-crun
ci/prow/verify-commits 9412137 link true /test verify-commits
ci/prow/e2e-aws-ovn-runc 9412137 link true /test e2e-aws-ovn-runc
ci/prow/e2e-aws-ovn-cgroupsv2 9412137 link true /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-fips 9412137 link true /test e2e-aws-ovn-fips
ci/prow/e2e-aws-crun-wasm 9412137 link true /test e2e-aws-crun-wasm
ci/prow/k8s-e2e-gcp-ovn 9412137 link true /test k8s-e2e-gcp-ovn
ci/prow/k8s-e2e-gcp-serial 9412137 link true /test k8s-e2e-gcp-serial

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.

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants