-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Update to Go 1.16.1 #5056
Update to Go 1.16.1 #5056
Conversation
/test all |
/test pull-containerd-build |
1 similar comment
/test pull-containerd-build |
@dims not sure how to figure out the e2e failure as it appears containerd isn't running (the socket file does not exist), but I don't see any errors explaining why it isn't.. |
|
/test pull-containerd-node-e2e |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (if green)
/test pull-containerd-node-e2e |
1 similar comment
/test pull-containerd-node-e2e |
/test pull-containerd-build |
/test pull-containerd-node-e2e |
@dims any ideas? originally the problem was that the wrong bucket was being looked in because I added a commit between the "working"
Seems now that we aren't running CRI tests regularly post-merge maybe things are getting stale--we probably need to find some actions magic to trigger node-e2e tests on any commits that change CRI code or just run it daily via actions cron? |
/test pull-containerd-node-e2e going to try one last time to see if the gingko permission problem still persists. i don't think it will work as the underlying issue i saw in #5056 (comment) is still there. will dig into this more today |
failed : Looks like we introduced a |
screen shot from https://storage.googleapis.com/cri-containerd-staging/ : |
Build succeeded.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Looks like go1.16.1 comes out tomorrow. Probably makes sense to wait and update to that? |
@kevpar agreed; it's out but actions env hasn't updated their config file yet.. usually within 24 hours. As soon as it's available I'll update the PR |
Signed-off-by: Phil Estes <estesp@amazon.com>
Build succeeded.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
whoot ... time to move up local development environment to go 1.16.1! |
Removed the cherry pick since we now have #5178 after the quick turnaround of another Go point release. |
Update to Go 1.16.1 release
Signed-off-by: Phil Estes estesp@amazon.com