-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/dist: make --compile-only
actually only compile test binaries and not run them
#58297
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
Comments
Change https://go.dev/cl/464956 mentions this issue: |
For additional context, this comment thread captures some of the reasons why |
The previous change added a StopAfterMake requirement so that the misc-compile builders would only ever run make.bash. However, this is a fairly big hammer as it skips everything after make.bash. Coming up, we're going to want to runSubrepoTests. However, we can't call into runTests because of golang/go#58297, so we need a special exception for that. This change thus also adds the notion of IsCrossCompileOnly defined by whether the host arch doesn't line up with the target arch, and adds a test to make sure this only applies to the misc-compile builders. This change also removes some hard-coding of the misc-compile prefix in favor of this new IsCrossCompileOnly notion. For golang/go#58163. Change-Id: I40ce91e13b45e8bbbb607aedd302f0ec0fbd608a Reviewed-on: https://go-review.googlesource.com/c/build/+/464956 TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Run-TryBot: Michael Knyszek <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]>
There were a lot of internal refactors and clean up work done as part So this is done in Go 1.21. |
Currently the
--compile-only
flag mostly prevents tests from running, but still runs all compiled test binaries. This means that our cross-compiling builders don't have an easy way to build test packages, so we're missing some coverage there on the trybots.CC @aclements @golang/release
The text was updated successfully, but these errors were encountered: