-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
bump ci go version to 1.5.1 #13838
bump ci go version to 1.5.1 #13838
Conversation
GCE e2e build/test passed for commit 394d474e6bf14cce926762b57b899e8dc3f54505. |
+1 FWIW you can make Travis run on 1.4 as well as 1.5.1 too. |
Still getting 500's on shippable. |
I restarted shippable-- is it fixed today? |
@lavalamp still a 500:
|
Well it's green. 👍. I'm going to restart it a couple times. |
GCE e2e build/test failed for commit 885738a2a172814c0ff23d69a32ab73f06522fb4. |
4 races
|
One data race in testclient, two in github.com/coreos/go-oidc/oidc, and one in net/http and scheduler |
I can have a quick look later today. |
Labelling this PR as size/S |
Jenkins e2e failure was a flaky test. @k8s-bot test this again please |
However shippable failure's are not flakes :( |
GCE e2e build/test failed for commit 885738a2a172814c0ff23d69a32ab73f06522fb4. |
The |
The oidc one looks like a bug in go-oidc... need to dig more. |
I've also sent out #18499 out for review which should fix one more data-race. I think that for all problems in this PR, there are currently PRs under review fixing them. |
So just to summarize:
|
Restarting to see where we are now. @k8s-bot unit test this please |
OK - it's much better now. The failing tests are:
The last 3 failures are exactly the same - I opened #18701 for it. |
hmm - #18449 fixed one problem, but there is one more there. So to summarize - there are two issues left: |
It seems that we are now only waiting for these PRs to be merged: Both are already LGTM-ed, so we should be ready to go with this PR soon. |
GCE e2e test build/test passed for commit c2753d7. |
We are all green - yay! |
I vote for applying "LGTM" label on this PR and merging it. @thockin @brendandburns @mikedanese - any objections? |
I really want to click the button, but since I'm out in an hour, that's probably not nice of me. We have clean tests, I say GO. |
After discussing with @thockin and @brendandburns we are going to merge it soon. Applying "LGTM" label (we will revert in case of significant issues). |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e test build/test passed for commit c2753d7. |
Automatic merge from submit-queue |
Auto commit by PR queue bot
Related #18907; codecgen appears to behave differently under go 1.4 and 1.5; Travis runs 1.5 and fails diffs generated by 1.4. |
yeah - I'm afraid we have a bunch of problems with unit test too |
I'm no longer certain that the problem is the golan version; I've had a couple situations where I did a hack/update-all.sh and then verify-all.sh failed on codecgen. When I ran hack/update-codecgen manually after that, and reverified, it worked. Will open a new issue to track that. |
[TESTING] redo of #12967, thanks @mvdan for fixing all the tests.