-
Notifications
You must be signed in to change notification settings - Fork 18k
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
crypto/internal/fips140test:gofips140-v1.0.0: TestACVP failures #71508
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Comments
Found new dashboard test flakes for:
2025-01-30 21:39 gotip-windows-amd64-longtest go@ce7ea0a6 crypto/internal/fips140test:gofips140-v1.0.0.TestACVP (log)
|
Found new dashboard test flakes for:
2025-01-29 15:10 gotip-windows-amd64-longtest go@e81f7155 crypto/internal/fips140test:gofips140-v1.0.0.TestACVP (log)
|
Found new dashboard test flakes for:
2025-01-29 15:10 go1.24-windows-amd64-longtest release-branch.go1.24@e81f7155 crypto/internal/fips140test:gofips140-v1.0.0.TestACVP (log)
2025-01-30 21:39 go1.24-windows-amd64-longtest release-branch.go1.24@ce7ea0a6 crypto/internal/fips140test:gofips140-v1.0.0.TestACVP (log)
|
Change https://go.dev/cl/645895 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Feb 3, 2025
Trying to find out why "go env GOMODCACHE" is failing on the Windows longtest builder. For #71508 Change-Id: I0642d5a5d85a549c6edde0be5bed8f0a16cca200 Cq-Include-Trybots: luci.golang.try:gotip-windows-amd64-longtest Reviewed-on: https://go-review.googlesource.com/c/go/+/645895 Reviewed-by: Roland Shoemaker <roland@golang.org> Auto-Submit: Ian Lance Taylor <iant@google.com> Reviewed-by: Ian Lance Taylor <iant@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: