-
Notifications
You must be signed in to change notification settings - Fork 3.9k
build: require go1.12 #38379
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
build: require go1.12 #38379
Conversation
a16da8a
to
521a52d
Compare
Some more tweaks. |
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.
I have another go 1.12-related cleanup in #38384.
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.
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @andreimatei and @petermattis)
build/teamcity-assert-clean.sh, line 13 at r1 (raw file):
git diff -a >&2 || true echo "Nuking build cruft. Please teach this build to clean up after itself." >&2 run docker run --volume="$root:/nuke" --workdir="/nuke" golang:stretch /bin/bash -c "git clean -ffdx ; git submodule foreach --recursive git clean -xffd" >&2
This will automatically use 1.13 when that's released, no? Is that desirable?
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.
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @petermattis and @RaduBerinde)
build/teamcity-assert-clean.sh, line 13 at r1 (raw file):
Previously, RaduBerinde wrote…
This will automatically use 1.13 when that's released, no? Is that desirable?
I thought so... To be honest I don't understand what this docker invocation does; how does it use go?
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.
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @petermattis and @RaduBerinde)
build/teamcity-assert-clean.sh, line 13 at r1 (raw file):
Previously, andreimatei (Andrei Matei) wrote…
I thought so... To be honest I don't understand what this docker invocation does; how does it use go?
I guess it's just a random image that has git in it. Now the question is why does it use docker... Jordan says that maybe the system git is too old. 🤷♂️
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.
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @andreimatei and @petermattis)
build/teamcity-assert-clean.sh, line 13 at r1 (raw file):
Previously, andreimatei (Andrei Matei) wrote…
I guess it's just a random image that has git in it. Now the question is why does it use docker... Jordan says that maybe the system git is too old. 🤷♂️
Oh.. I didn't notice it just runs git. Weird.
There is another invocation here:
# NB: Using golang:1.11.5-stretch instead of golang:stretch because of #35637. |
For that one my question stands. I think we should fix that to 1.12 or things might break when 1.13 gets released.
521a52d
to
4d0ba9b
Compare
Since the builder was upgraded a while ago and we already have code needing 1.12. Some assembly files no longer have any (intended) effect in go 1.12, and their existence has proven surprisingly troublesome as their comments indicated. Closes cockroachdb#35637 Release note: The minimum compiler version for building CRDB is now go 1.12.
4d0ba9b
to
a8b7483
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.
Took over #38384 here.
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @petermattis and @RaduBerinde)
build/teamcity-assert-clean.sh, line 13 at r1 (raw file):
Previously, RaduBerinde wrote…
Oh.. I didn't notice it just runs git. Weird.
There is another invocation here:
# NB: Using golang:1.11.5-stretch instead of golang:stretch because of #35637. For that one my question stands. I think we should fix that to 1.12 or things might break when 1.13 gets released.
yup, fixed that one. Thanks.
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.
bors r+
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @petermattis and @RaduBerinde)
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.
bors please
bors+
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @petermattis and @RaduBerinde)
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.
bors r+
Reviewable status:
complete! 0 of 0 LGTMs obtained (waiting on @petermattis and @RaduBerinde)
Build succeeded |
Since the builder was upgraded a while ago and we already have code
needing 1.12.
Release note: The minimum compiler version for building CRDB is now go
1.12.