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

ci/circleci: go version differs from what is in .circleci/config.yml #2331

Closed
HaoyangLiu opened this issue Sep 13, 2018 · 11 comments
Closed

Comments

@HaoyangLiu
Copy link

I created a PR and it invoked a circleci test. But the cicleci test failed

If the golang version is later than 1.10, my PR won't encounter circleci test failure. But the golang version of cicleci test docker image is 1.9.1. My point is why we still use golang 1.9.1 to run circleci test. Can someone help to clarify this issue?

@alexanderbez
Copy link
Contributor

We should probably update this to 1.11.

@fedekunze fedekunze changed the title ci/circleci: use golang 1.9.1 ci/circleci: update Go version Sep 13, 2018
@ValarDragon
Copy link
Contributor

ValarDragon commented Sep 14, 2018

I don't think we should update CI to 1.11. We currently state that we support 1.10+, so CI should be running on 1.10. CI is currently on 1.10.3

@ValarDragon
Copy link
Contributor

Oh huh, even though .circleci states its on 1.10.3, in your PR its running 1.9. I'm not sure whats going on.

@HaoyangLiu
Copy link
Author

The docker image name of CI is circleci/golang:1.10.3. But actually, the golang version is 1.9.1

@ValarDragon ValarDragon changed the title ci/circleci: update Go version ci/circleci: go version differs from what is in .circleci/config.yml Sep 14, 2018
@HaoyangLiu
Copy link
Author

Maybe there is something wrong in the docker image

@alexanderbez
Copy link
Contributor

alexanderbez commented Sep 14, 2018

We currently state that we support 1.10+

@ValarDragon but we don't atm. Try building develop. Ref: #2253

We should fix whatever dependencies we need to to continue to support 1.10 or state otherwise.

@ValarDragon
Copy link
Contributor

It works for me on 1.10.1. If we come to consensus on just dropping on 1.10 support, thats fine. (I'll just go ahead and upgrade :() Until then though, I think CI should remain 1.10. (I'm in favor of supporting 1.10 until we want some 1.11 feature)

@alexanderbez
Copy link
Contributor

Mhmmm, you tried building cleanly off of the latest develop? Strange....

@ValarDragon
Copy link
Contributor

Yup, make get_vendor_deps, make install succeeds for me on develop.

@alexanderbez
Copy link
Contributor

haha, ok, I take back my statement then 👍

@cwgoes
Copy link
Contributor

cwgoes commented Oct 9, 2018

Fixed.

@cwgoes cwgoes closed this as completed Oct 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants