Skip to content

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

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.

Sign up for GitHub

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

Jump to bottom
Closed
tianxiaogu opened this issue Mar 25, 2025 · 3 comments
Closed

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

tianxiaogu opened this issue Mar 25, 2025 · 3 comments
Labels
BugReport Issues describing a possible bug in the Go implementation. compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Testing An issue that has been verified to require only test changes, not just a test failure. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.

Comments

@tianxiaogu
Copy link

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
Copy link

Related Issues

Related Code Changes

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

@gabyhelp gabyhelp added the BugReport Issues describing a possible bug in the Go implementation. label Mar 25, 2025
@dmitshur dmitshur added Testing An issue that has been verified to require only test changes, not just a test failure. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. compiler/runtime Issues related to the Go compiler and/or runtime. labels Mar 25, 2025
@dmitshur
Copy link
Contributor

Is this the same as issue #18222?

@dmitshur dmitshur added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Mar 25, 2025
@gopherbot
Copy link
Contributor

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.)

@gopherbot gopherbot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
BugReport Issues describing a possible bug in the Go implementation. compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. Testing An issue that has been verified to require only test changes, not just a test failure. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
Go Compiler / Runtime
Status: Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tianxiaogu @dmitshur @gopherbot @gabyhelp