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.
For additional context, this comment thread captures some of the reasons why -run=^$ was chosen over test -c at the time, before we considered this use case.
gopherbot
pushed a commit
to golang/build
that referenced
this issue
Feb 3, 2023
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 <gobot@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Run-TryBot: Michael Knyszek <mknyszek@google.com>
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
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: