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

github.com/onsi/ginkgo v1.6.0 #76652

Merged
merged 1 commit into from Apr 17, 2019
Merged

Conversation

liggitt
Copy link
Member

@liggitt liggitt commented Apr 16, 2019

Bumps ginkgo to the version preferred by our current level of github.com/onsi/gomega

What type of PR is this?
/kind cleanup

Does this PR introduce a user-facing change?:

NONE

/area code-organization
/sig testing

/cc @dims
for dependency bump

/cc @BenTheElder
for testing dependency

/cc @cblecker
for license addition

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. area/code-organization Issues or PRs related to kubernetes code organization sig/testing Categorizes an issue or PR as relevant to SIG Testing. approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 16, 2019
@liggitt
Copy link
Member Author

liggitt commented Apr 16, 2019

/priority important-soon

with this bump, all our dependencies are at their natural versions with the exception of golang/x/{sys,tools} which are at the go1.12 branch levels

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Apr 16, 2019
@liggitt
Copy link
Member Author

liggitt commented Apr 16, 2019

/hold
for review by all assigned

@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. area/apiserver area/cloudprovider area/dependency Issues or PRs related to dependency changes sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels Apr 16, 2019
@dims
Copy link
Member

dims commented Apr 16, 2019

@liggitt looks like we will have 2 fsnotify packages with this change (with same code?)

  • gopkg.in/fsnotify.v1
  • github.com/fsnotify/fsnotify

Anything we can do to collapse them?

@liggitt
Copy link
Member Author

liggitt commented Apr 16, 2019

Anything we can do to collapse them?

We'd have transitive dependencies on both (github.com/spf13/viper/viper.go uses github.com/fsnotify/fsnotify), so not easily

@liggitt liggitt changed the title github.com/onsi/ginkgo v1.6.0 WIP - github.com/onsi/ginkgo v1.6.0 Apr 16, 2019
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 16, 2019
@dims
Copy link
Member

dims commented Apr 16, 2019

@liggitt other than that the tomb and tail dependency seem ok (other than a note in kubernetes/node-problem-detector#3 where folks ran into a problem with hpcloud/tail)

@liggitt
Copy link
Member Author

liggitt commented Apr 16, 2019

@liggitt other than that the tomb and tail dependency seem ok (other than a note in kubernetes/node-problem-detector#3 where folks ran into a problem with hpcloud/tail)

it looks like that's only in use by the ginkgo DebugParallel function, which I don't see us using

@liggitt
Copy link
Member Author

liggitt commented Apr 16, 2019

/retest

@liggitt liggitt changed the title WIP - github.com/onsi/ginkgo v1.6.0 github.com/onsi/ginkgo v1.6.0 Apr 16, 2019
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 16, 2019

tomb - support for clean goroutine termination in Go.

Copyright (c) 2010-2011 - Gustavo Niemeyer <gustavo@niemeyer.net>
Copy link
Member Author

Choose a reason for hiding this comment

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

hmm... this license doesn't have a recognized name... @cblecker, does the text match a known/acceptable license?

Copy link
Member Author

Choose a reason for hiding this comment

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

ah, looks to match the bsd 3-clause license, but extra eyes are appreciated

Copy link
Member

@neolit123 neolit123 Apr 16, 2019

Choose a reason for hiding this comment

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

looks like the 3 clause BSD:
https://opensource.org/licenses/BSD-3-Clause

Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.

is not exactly something that certain parties want to comply with.
i'd ask the license experts.

Copy link
Member Author

Choose a reason for hiding this comment

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

we already have 14 other dependencies with this license, fyi

Copy link
Member

Choose a reason for hiding this comment

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

in that case we can assume it's OK.

Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

nice list, thanks.

@cblecker
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 17, 2019
Copy link
Member

@BenTheElder BenTheElder left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, cblecker, liggitt

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

@liggitt
Copy link
Member Author

liggitt commented Apr 17, 2019

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 17, 2019
@k8s-ci-robot k8s-ci-robot merged commit e4a4365 into kubernetes:master Apr 17, 2019
@liggitt liggitt deleted the ginkgo branch April 17, 2019 19:23
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. area/apiserver area/cloudprovider area/code-organization Issues or PRs related to kubernetes code organization area/dependency Issues or PRs related to dependency changes cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note-none Denotes a PR that doesn't merit a release note. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants