-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
cmd/go: in 1.23rc2, TestScript fails on Windows when GOEXPERIMENT is set: "go was invoked but no counters were incremented" #68579
Comments
If I delete |
I can reproduce on Windows (though not on macOS) so this might be a Windows-specific issue. I'll try to find a fix. |
It didn't happen for me on Linux either, I agree it's probably specific to running on Windows. |
cc @findleyr Running the test on windows it seems to be writing counters to a file called We get the following error trying to open the file: I think that we expect that when the version name is not a devel version, say "go1.23rc2" that the version name doesn't contain anything other than the version name, but with GOEXPERIMENTS it adds the experiment names to the version. I think we should probably? mark those as devel. |
You should avoid using column ":" in the Windows file names. Just in case you did not know that. Alex |
This was fixed in x/telemetry by https://go.dev/cl/603855, which was vendored into cmd/ with https://go.dev/cl/603898 |
Go version
go version go1.23rc2 windows/amd64
Output of
go env
in your module/workspace:What did you do?
In pwsh, in
src
:(Many other TestScripts will fail in this situation because they share the telemetry check, but I chose this one as an example with relatively low output.)
What did you see happen?
If I don't limit the test run, many other test scripts fail with the same error
script_test.go:401: go was invoked but no counters were incremented
.I got the same bad result with
$env:GOEXPERIMENT='arenas'
.What did you expect to see?
I got this result with
go version devel go1.24-792a261303 Wed Jul 24 18:59:46 2024 +0000 windows/amd64
on the same machine.The text was updated successfully, but these errors were encountered: