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

Vendoring is broken? #166

Closed
msau42 opened this issue Aug 10, 2019 · 7 comments
Closed

Vendoring is broken? #166

msau42 opened this issue Aug 10, 2019 · 7 comments

Comments

@msau42
Copy link
Collaborator

msau42 commented Aug 10, 2019

Checked out a fresh master branch and ran "make test":

### test-vendor:
Repo uses 'dep' for vendoring.
# vendor is out of sync:
github.com/googleapis/gnostic: hash of vendored tree not equal to digest in Gopkg.lock
make: *** [release-tools/build.make:132: test-vendor] Error 1

$ dep version
dep:
 version     : v0.5.1
 build date  : 2019-03-11
 git hash    : faa6189
 go version  : go1.12
 go compiler : gc
 platform    : linux/amd64
 features    : ImportDuringSolve=false
@msau42
Copy link
Collaborator Author

msau42 commented Aug 10, 2019

@msau42
Copy link
Collaborator Author

msau42 commented Aug 10, 2019

cc @pohly

@pohly
Copy link
Contributor

pohly commented Aug 26, 2019 via email

@pohly
Copy link
Contributor

pohly commented Aug 29, 2019

I submitted an enhancement for the vendor check with dep under Prow here: kubernetes-csi/csi-release-tools#27

@jsafrane
Copy link
Contributor

The PR from the previous comment was merged, is this issue fixed now?

@msau42
Copy link
Collaborator Author

msau42 commented Sep 19, 2019

test-vendor is running properly in prow now:
https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/kubernetes-csi_external-attacher/182/pull-kubernetes-csi-external-attacher-unit/1173926579315675136/build-log.txt

So maybe this is just some problem with my local environment.
/close

@k8s-ci-robot
Copy link
Contributor

@msau42: Closing this issue.

In response to this:

test-vendor is running properly in prow now:
https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/kubernetes-csi_external-attacher/182/pull-kubernetes-csi-external-attacher-unit/1173926579315675136/build-log.txt

So maybe this is just some problem with my local environment.
/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
None yet
Projects
None yet
Development

No branches or pull requests

4 participants