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

DO NOT MERGE: prototype openshift-tests wrapper/separation #1433

Closed
wants to merge 2 commits into from

Conversation

bparees
Copy link

@bparees bparees commented Dec 6, 2022

goes along with openshift/origin#27563

@bparees bparees changed the title <!-- Thanks for sending a pull request! Here are some tips for you: DO_NOT_MERGE: prototype openshift-tests wrapper/separation Dec 6, 2022
@bparees bparees changed the title DO_NOT_MERGE: prototype openshift-tests wrapper/separation DO NOT MERGE: prototype openshift-tests wrapper/separation Dec 6, 2022
@bparees bparees added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 6, 2022
@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Dec 6, 2022
@openshift-ci-robot
Copy link

@bparees: 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.

1 similar comment
@openshift-ci-robot
Copy link

@bparees: 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 openshift-ci bot added the vendor-update Touching vendor dir or related files label Dec 6, 2022
@openshift-ci
Copy link

openshift-ci bot commented Dec 6, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bparees
Once this PR has been reviewed and has the lgtm label, please assign sttts for approval by writing /assign @sttts in a comment. 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

@bparees: 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.

github.com/onsi/ginkgo => github.com/onsi/ginkgo v1.11.0
github.com/onsi/ginkgo/v2 => github.com/openshift/onsi-ginkgo/v2 v2.0.0-20221104153651-0e2187c0d222
github.com/openshift/library-go => github.com/openshift/library-go v0.0.0-20221101142545-76526edf66e8
github.com/openshift/origin => github.com/bparees/origin v0.0.0-20221207195106-867dedaea002
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

naughty. This shouldn't be here.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

meaning the origin dep in general? yeah, ultimately we probably need to factor some code out into a new repo and then have origin + o/k both dep that code.

luckily it is not that much code at this point so i don't think it'll be too terrible to do.

@@ -35,11 +35,21 @@ require (
)

replace (
github.com/containerd/containerd => github.com/containerd/containerd v1.4.9
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this stands out as a likely diamond. What's it for?

github.com/imdario/mergo => github.com/imdario/mergo v0.3.6
github.com/matttproud/golang_protobuf_extensions => github.com/matttproud/golang_protobuf_extensions v1.0.1
github.com/onsi/ginkgo/v2 => github.com/openshift/onsi-ginkgo/v2 v2.0.0-20221005160638-5fa9cd70cd8c
github.com/mohae/deepcopy => github.com/mohae/deepcopy v0.0.0-20170603005431-491d3605edfb
github.com/onsi/ginkgo => github.com/onsi/ginkgo v1.11.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

v1 ginkgo looks off.

@deads2k
Copy link

deads2k commented Dec 13, 2022

some of the deps look off, but I like the idea here. The wrapper doesn't look awful. I wonder if we actually need to instantiate all the providers since we're going to execve eventually anyway, right?

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 16, 2022
@openshift-merge-robot
Copy link

@bparees: PR needs rebase.

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

openshift-ci bot commented Jan 6, 2023

@bparees: 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/images 8641b62 link true /test images
ci/prow/4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade 8641b62 link false /test 4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade
ci/prow/e2e-aws-csi 8641b62 link false /test e2e-aws-csi
ci/prow/e2e-aws-ovn-cgroupsv2 8641b62 link true /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-gcp 8641b62 link true /test e2e-gcp
ci/prow/verify-commits 8641b62 link true /test verify-commits
ci/prow/e2e-aws-ovn-fips 8641b62 link true /test e2e-aws-ovn-fips
ci/prow/k8s-e2e-aws-ovn-serial 8641b62 link false /test k8s-e2e-aws-ovn-serial
ci/prow/k8s-e2e-gcp-serial 8641b62 link true /test k8s-e2e-gcp-serial
ci/prow/k8s-e2e-conformance-aws 8641b62 link true /test k8s-e2e-conformance-aws
ci/prow/e2e-agnostic-ovn-cmd 8641b62 link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-ovn-crun 8641b62 link true /test e2e-aws-ovn-crun
ci/prow/e2e-aws-serial 8641b62 link true /test e2e-aws-serial
ci/prow/k8s-e2e-gcp-ovn 8641b62 link true /test k8s-e2e-gcp-ovn
ci/prow/e2e-gcp-ovn-upgrade 8641b62 link true /test e2e-gcp-ovn-upgrade
ci/prow/e2e-aws-ovn-downgrade 8641b62 link true /test e2e-aws-ovn-downgrade
ci/prow/e2e-aws-ovn-serial 8641b62 link true /test e2e-aws-ovn-serial
ci/prow/e2e-azure-ovn-upgrade 8641b62 link true /test e2e-azure-ovn-upgrade
ci/prow/e2e-aws-ovn-upgrade 8641b62 link true /test e2e-aws-ovn-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-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 7, 2023
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 7, 2023
@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Jun 7, 2023
@openshift-ci
Copy link

openshift-ci bot commented Jun 7, 2023

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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/test-infra repository.

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/hold Indicates that a PR should not merge because someone has issued a /hold command. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants