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

Travis CI failing with undefined proto errors for trivial text change PR's #377

Closed
davidz627 opened this issue Aug 8, 2019 · 12 comments · Fixed by #378
Closed

Travis CI failing with undefined proto errors for trivial text change PR's #377

davidz627 opened this issue Aug 8, 2019 · 12 comments · Fixed by #378

Comments

@davidz627
Copy link
Contributor

For example this PR is just text change: #375

CI is failing here: https://travis-ci.org/container-storage-interface/spec/jobs/569485934

The error:

go install ./csi
# google.golang.org/genproto/googleapis/rpc/status
../../../../../google.golang.org/genproto/googleapis/rpc/status/status.pb.go:23:11: undefined: proto.ProtoPackageIsVersion3
make: *** [csi.a] Error 2
make: Leaving directory `/home/travis/gopath/src/github.com/container-storage-interface/spec/lib/go'

My assumption is one of the proto libraries/grpc version is unpinned in CI and the golang (and some other stuff) has pinned versioning. So just every once in a while CI will break for no reason.

This is an issue with the Spec. Generating the protos on a local machine isn't much better to be honest, it's always an exercise in figuring out the correct package versions to have on my workstation...

/assign @jdef @saad-ali @jieyu @julian-hj

@jieyu
Copy link
Member

jieyu commented Aug 8, 2019

We really need to move to a docker based build environment.

@saad-ali
Copy link
Member

saad-ali commented Aug 9, 2019

We really need to move to a docker based build environment.

@hakanmemisoglu: It is asking a lot, but would you be interested and willing to do this?

@tdmanv
Copy link
Contributor

tdmanv commented Aug 9, 2019

@saad-ali Hakan is a bit swamped at the moment, but I have some time to help out. Do you have a preference for where to put the Dockerfile and upload an image? It looks like https://hub.docker.com/_/golang is almost enough to run the travis commands. The only thing missing is unzip

@tdmanv
Copy link
Contributor

tdmanv commented Aug 9, 2019

@saad-ali This instance of the issue is fixed by #378.

We can also help with containerizing the build environment, but we would need to discuss where to put the Dockerfile and host the image.

@saad-ali
Copy link
Member

saad-ali commented Aug 10, 2019

@tdmanv thank you very much, that would be great. Let's put it in https://quay.io/organization/k8scsi
If you share your quay username with me (feel free to email me, if you prefer), I can invite you to that org

@tdmanv
Copy link
Contributor

tdmanv commented Aug 10, 2019

@saad-ali I don't mind: https://quay.io/user/tdmanv

@saad-ali
Copy link
Member

saad-ali commented Aug 12, 2019

@tdmanv invite to the org sent! Feel free to create a new repo called csi-spec or spec or something for the image in that org. Thanks again. Also there are a bunch of scripts that the kubernetes-csi repo uses to push to quay, see https://github.com/kubernetes-csi/csi-release-tools (you may be able to barrow things from there).

@tdmanv
Copy link
Contributor

tdmanv commented Aug 12, 2019

Great thanks for the pointer.

My preference would be to first merge #378, which is required no matter what and will immediately unblock the other PRs. After I can followup with dockerizing the build. It requires makefile and travis changes so it will take a bit longer.

What do you think?

@saad-ali
Copy link
Member

SGTM. Merged 378

@saad-ali
Copy link
Member

@tdmanv can you and @hakanmemisoglu also make sure to sign the CLA. I also sent you an email with instructions.

@tdmanv
Copy link
Contributor

tdmanv commented Aug 14, 2019

Done! Thank you.

@saad-ali
Copy link
Member

Thank you!

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

Successfully merging a pull request may close this issue.

4 participants