-
Notifications
You must be signed in to change notification settings - Fork 440
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 go 1.22.1 (with fix for dockerfiles) #1764
Conversation
eb68b71
to
8685637
Compare
8685637
to
e2d814e
Compare
e2d814e
to
6952e54
Compare
Link to presubmit tests passing log: logs |
6952e54
to
1c51816
Compare
Marking as draft until I try out the switch to |
f3af723
to
d45d298
Compare
36971eb
to
50d2f6f
Compare
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.
Changes look good to me, other than one confirmation comment.
Other than that, as we discussed offline.
- We should sanity it by running it with louhi test-flow.
- Also, should check the impact of these changes with GKE team.
2106bc6
to
3e2ecde
Compare
Ran it once and build went through. I have given it another run after adding the
Will check with @songjiaxun . |
Does the following 1. Create a go module (go.mod) in a directory package_gcsfuse, to bypass the change in go get behaviour introduced in 1.17 and enforced in go 1.22. 2. Fix some paths and commands etc. accordingly in the dockerfile.
Does the following 1. Create a go module (go.mod) in a directory package_gcsfuse, to bypass the change in go get behaviour introduced in 1.17 and enforced in go 1.22. 2. Fix some paths and commands etc. accordingly in the dockerfile.
Fetch only the last commit state in docker files during git clone to reduce its runtime. This reduces the runtime of git clone dramatically.
3e2ecde
to
1144c0a
Compare
I checked Louhi test-flow with
@songjiaxun shared over chat that "GKE Louhi pipeline and the testgrid uses tools/package_gcsfuse_docker/Dockerfile to build gcsfuse binary, so as long as the Dockerfile works, out pipeline should be fine.". So I think we're good there. Also, I upgraded this PR to 1.22.1 (from 1.22) as @songjiaxun requested. |
@raj-prince please approve this. This has passed the integration and perf tests, and louhi-test workflow. |
* Upgrade to golang 1.22 (without dockerfile fix) Reapply "Upgrade to golang 1.22 (#1753)" (#1766) This reverts commit a63a46f and fixes merge conflicts with golang 1.21.7 upgrade which went in earlier. * Fix containerize_gcsfuse/dockerfile for go 1.22 Does the following 1. Create a go module (go.mod) in a directory package_gcsfuse, to bypass the change in go get behaviour introduced in 1.17 and enforced in go 1.22. 2. Fix some paths and commands etc. accordingly in the dockerfile. * Fix package_gcsfuse/dockerfile for go 1.22 Does the following 1. Create a go module (go.mod) in a directory package_gcsfuse, to bypass the change in go get behaviour introduced in 1.17 and enforced in go 1.22. 2. Fix some paths and commands etc. accordingly in the dockerfile. * Switch containerize*/Dockerfile to use git clone * Switch package*/Dockerfile to use git clone * Replace /go with ${GOPATH} * Minimize run of git clone Fetch only the last commit state in docker files during git clone to reduce its runtime. This reduces the runtime of git clone dramatically. * Upgrade from go 1.22.0 to 1.22.1
Description
This reverts commit a63a46f.
go get
error, by switching togit clone
(in the docker container).Link to the issue in case of a bug fix.
NA
Testing details