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

Upgrade to golang 1.6 #22149

Merged
merged 1 commit into from
Apr 5, 2016
Merged

Upgrade to golang 1.6 #22149

merged 1 commit into from
Apr 5, 2016

Conversation

luxas
Copy link
Member

@luxas luxas commented Feb 28, 2016

A second attempt to upgrade go version above go1.4
Merge ASAP after you've cut the release-1.2 branch and feel ready.
go1.6 should perform slightly better than go1.5, so this time it might work
@gmarek @wojtek-t @zmerlynn @mikedanese @brendandburns @ixdy @thockin

@k8s-bot
Copy link

k8s-bot commented Feb 28, 2016

GCE e2e build/test failed for commit 18f520dccd552134dec2bff5015df859fe9222e9.

Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake.

@k8s-github-robot
Copy link

Labelling this PR as size/M

@k8s-github-robot k8s-github-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 28, 2016
@luxas
Copy link
Member Author

luxas commented Feb 28, 2016

@mikedanese Should we have an option to force build the kube-cross image when necessary?
In these cases that's needed.

@@ -15,7 +15,7 @@
# This file creates a standard build environment for building cross
# platform go binary for the architecture kubernetes cares about.

FROM golang:1.4.2
FROM golang:1.6
Copy link
Member

Choose a reason for hiding this comment

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

please include the minor version. e.g. 1.6.0

@mikedanese
Copy link
Member

.travis.yml and shippable.yml also need the version bump

@mikedanese mikedanese assigned wojtek-t and unassigned zmerlynn Feb 28, 2016
@mikedanese
Copy link
Member

Should we have an option to force build the kube-cross image when necessary?
In these cases that's needed.

What would it do? We need to push kube-cross before CI goes green right now. That seems like a reasonable check to have

@luxas
Copy link
Member Author

luxas commented Feb 28, 2016

@mikedanese Fixed. Now the kube-cross will be built if it isn't pushed.

@mikedanese
Copy link
Member

I don't think that's a good idea. It allows CI to pass without pushing the image first which is a bad thing.

@luxas
Copy link
Member Author

luxas commented Feb 28, 2016

I'm fine with that. Do you have a better approach?

@k8s-bot
Copy link

k8s-bot commented Feb 28, 2016

GCE e2e build/test failed for commit f6472f5d9d173e2276f44bafa3497c9799c9955d.

Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake.

@luxas
Copy link
Member Author

luxas commented Feb 28, 2016

@mikedanese OK, what do you say about this then?
We'll update non-release CI to go1.6 in this PR before v1.2.
If you want, we may also merge the bump to go1.6 in build/build-image/cross before v1.2
If we do that, you should push v1.6.0-1 to gcr.io, but we'll not use it in build/common.sh for v1.2

If a v1.6.0-1 image would be pushed somehow, it would help a lot!

@k8s-bot
Copy link

k8s-bot commented Feb 28, 2016

GCE e2e build/test passed for commit 0fb8245a607dde8290ed467e85cb3655ef880c64.

@k8s-github-robot
Copy link

The author of this PR is not in the whitelist for merge, can one of the admins add the 'ok-to-merge' label?

@wojtek-t
Copy link
Member

Well - we deinifetly do not want to have this for 1.2, so I will get back to it once we are done with our 1.2 work.

@luxas
Copy link
Member Author

luxas commented Feb 29, 2016

Yeah, as I said in the first place. Didn't think you'd want it either. But just asked anyway...
I'm ready when you are ready :)

@@ -15,7 +15,7 @@
# This file creates a build environment for building and running kubernetes
# unit and integration tests

FROM golang:1.5.3
Copy link
Member

Choose a reason for hiding this comment

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

should update the tag for this image (in the Makefile) as well

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks. Fixed.

@k8s-bot
Copy link

k8s-bot commented Mar 1, 2016

GCE e2e build/test passed for commit 8647e666c0b82e702e904d07e98ad021162d7f48.

@wojtek-t
Copy link
Member

wojtek-t commented Mar 4, 2016

@luxas - FYI, we have a bunch of unit tests failing with Go 1.6, so there is long way to do before we do this...

@luxas
Copy link
Member Author

luxas commented Mar 4, 2016

Thanks for the info, good to know.
But really sad things are failing.
Would intermediate 1.4.2 => 1.5.3 => 1.6.0 be a better migration, so the step wouldn't be so huge?
Just thinking out loud...

@@ -4,7 +4,7 @@ language: go

matrix:
include:
- go: 1.5.3
- go: 1.6.0
Copy link
Member

Choose a reason for hiding this comment

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

@spxtr @ixdy
Since we are no longer using shippable - can't we just remove this whole file?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, probably best to do that in a separate PR though.

Copy link
Member

Choose a reason for hiding this comment

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

#23845 out for review

@lavalamp
Copy link
Member

lavalamp commented Apr 5, 2016

LGTM

@timothysc
Copy link
Member

Can someone apply the label, given multiple lgtms?

@eparis eparis added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 5, 2016
@eparis
Copy link
Contributor

eparis commented Apr 5, 2016

I'll be the one. /me wonders why @timothysc didn't do it :)

@k8s-github-robot
Copy link

@k8s-bot test this

Tests are more than 48 hours old. Re-running tests.

@timothysc
Copy link
Member

@eparis didn't want to stomp on toes. ;-)

@eparis
Copy link
Contributor

eparis commented Apr 5, 2016

STOMP!

@k8s-bot
Copy link

k8s-bot commented Apr 5, 2016

GCE e2e build/test passed for commit 2928d0a.

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Apr 5, 2016

GCE e2e build/test passed for commit 2928d0a.

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Apr 5, 2016

GCE e2e build/test passed for commit 2928d0a.

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Apr 5, 2016

GCE e2e build/test passed for commit 2928d0a.

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit 4f32951 into kubernetes:master Apr 5, 2016
@spxtr
Copy link
Contributor

spxtr commented Apr 5, 2016

Here we go!

It occurs to me that we might need to up the timeout on the kubernetes-build job. Nope, it's still well within the limit :)

@hongchaodeng
Copy link
Contributor

./test/e2e_node/jenkins/e2e-node-jenkins.sh seems to be using the go on host. This might still be using go 1.4 depending on the host.

@spxtr @luxas Is there any plan for keep that part up-to-date as well?

/cc @xiang90

@david-mcmahon david-mcmahon changed the title Up to golang 1.6 Upgrade to golang 1.6 Apr 6, 2016
k8s-github-robot pushed a commit that referenced this pull request Apr 6, 2016
Automatic merge from submit-queue

Add a note about supported go version

Broke out from #22149 
@wojtek-t
xingzhou pushed a commit to xingzhou/kubernetes that referenced this pull request Dec 15, 2016
Automatic merge from submit-queue

Up to golang 1.6

A second attempt to upgrade go version above `go1.4`
Merge ASAP after you've cut the `release-1.2` branch and feel ready.
`go1.6` should perform slightly better than `go1.5`, so this time it might work
@gmarek @wojtek-t @zmerlynn @mikedanese @brendandburns @ixdy @thockin
xingzhou pushed a commit to xingzhou/kubernetes that referenced this pull request Dec 15, 2016
Automatic merge from submit-queue

Add a note about supported go version

Broke out from kubernetes#22149 
@wojtek-t
openshift-publish-robot pushed a commit to openshift/kubernetes that referenced this pull request Feb 26, 2019
…-discovery

UPSTREAM: 00000: wait for CRD discovery to be successful once before

Origin-commit: 9ffad072ee9a512a7344dba700b5a15bcad5349a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.