-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: GOFIPS140=v1.0.0 makes tests flaky #71491
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
Labels
BugReport
Issues describing a possible bug in the Go implementation.
GoCommand
cmd/go
NeedsFix
The path to resolution is known, but the work has not been done.
release-blocker
Milestone
Comments
Change https://go.dev/cl/645835 mentions this issue: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
BugReport
Issues describing a possible bug in the Go implementation.
GoCommand
cmd/go
NeedsFix
The path to resolution is known, but the work has not been done.
release-blocker
Go version
HEAD
Output of
go env
in your module/workspace:What did you do?
GOFIPS140=v1.0.0 go test -test.count=10 crypto/x509 crypto/internal/fips140/...
What did you see happen?
What did you expect to see?
A series of lines starting with
ok
, indicating that all the tests passed.The problem is that setting
GOFIPS140
to a specific version causes the zip file in $GOROOT/lib/fips140 to be unpacked into the module cache each time that the go command is run. The crypto/x509 package has a test that runs the go command (TestImports
). Running that test in parallel with tests of other packages means that the contents of the module cache are being removed and recreated as tests are running. That causes failures like the one above, in which a file is missing just as a test is looking for it.Fixing this is a release blocker for 1.24.
The text was updated successfully, but these errors were encountered: