-
Notifications
You must be signed in to change notification settings - Fork 18k
crypto/internal/fips/aes/gcm: TestAllocations fails on PPC64 #70448
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
arch-ppc64x
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
Related Issues (Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.) |
Change https://go.dev/cl/629697 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Nov 19, 2024
TestAllocations is failing on PPC64 causing all PPC64 CI to fail. Skip the test until it can be debugged. For #70448 Change-Id: Ic18e402f4af5939a90eba2e1f2b182699013ed55 Reviewed-on: https://go-review.googlesource.com/c/go/+/629697 Reviewed-by: Filippo Valsorda <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Cherry Mui <[email protected]>
@golang/ppc64 |
Change https://go.dev/cl/636055 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Dec 13, 2024
TestXAESAllocations fails like #70448, and crypto/rand's fails in FIPS mode. We can't keep chasing these without even a LUCI builder. Updates #67307 Change-Id: I5d0edddf470180a321dec55cabfb018db62eb940 Reviewed-on: https://go-review.googlesource.com/c/go/+/636055 Auto-Submit: Filippo Valsorda <[email protected]> Reviewed-by: Roland Shoemaker <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Carlos Amedee <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
arch-ppc64x
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Go version
master
Output of
go env
in your module/workspace:What did you do?
cd crypto/internal/fips/aes/gcm
go test
What did you see happen?
--- FAIL: TestAllocations (0.00s)
ctrkdf_test.go:31: expected zero allocations, got 6.0
What did you expect to see?
All tests pass
The text was updated successfully, but these errors were encountered: