cmd/internal/testdir: testenv.go:166: skipping test: 'go build' not compatible with setting $GO_GCFLAGS

[tianxiaogu]

Go version

go version go1.22.8 darwin/amd64

Output of go env in your module/workspace:

GO111MODULE=''
GOARCH='amd64'
GOBIN=''

What did you do?

Run tests in test/ using cmd/internal/testdir with additional gcflags passed by GO_GCFLAGS.

What did you see happen?

cmd/internal/testdir obtains gcflags from the env variable GO_GCFLAGS, but the tool chain refuses to build and run tests if it detects GO_GCFLAGS. In my understanding, testdir cannot make use of GO_GCFLAGS. We may need another way to pass gcflags to the underlying tests.

testenv.go:166: skipping test: 'go build' not compatible with setting $GO_GCFLAGS

What did you expect to see?

Successfully run tests using cmd/internal/testdir with GO_GCFLAGS.

[gabyhelp]

Related Issues

• Bug: The go test command cannot parse custom args with flag.Parse() #39206 (closed)
• cmd/go: 'go test' not recognize '-ccflags' #7810 (closed)
• Go test breaks on flags in go 1.13 #34078 (closed)
• Cannot pass build flags to go test, go run #3196 (closed)
• go test broken with parameters #33869 (closed)
• cmd/go: go test -c does not apply specified gcflags to the test package #22831 (closed)
• test: doesn't use GO_GCFLAGS for tests #18222
• cmd/go: test with coverage unexpect fail #43242 (closed)
• cmd/internal/testdir: test fails when GOAMD64 is specified in goenv file #68548 (closed)

Related Code Changes

• test/run: make GO_GCFLAGS mean same thing it does during make.bash

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[dmitshur]

Is this the same as issue #18222?

[gopherbot]

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)