Skip to content
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

crypto/internal/fips/sha3: TestAllocations/New failures [consistent failure] #70421

Closed
gopherbot opened this issue Nov 18, 2024 · 4 comments
Closed

crypto/internal/fips/sha3: TestAllocations/New failures [consistent failure] #70421

gopherbot opened this issue Nov 18, 2024 · 4 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.

Comments

@gopherbot
Copy link
Contributor 

#!watchflakes
default <- pkg == "crypto/internal/fips/sha3" && test == "TestAllocations/New"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.01s)

— watchflakes
@gopherbot gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Nov 18, 2024
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "crypto/internal/fips/sha3" && test == "TestAllocations/New"
2024-11-18 18:26 gotip-linux-amd64-asan-clang15 go@7a20239c crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.01s)
2024-11-18 18:27 gotip-linux-amd64-asan-clang15 go@bcdaac63 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 18:28 gotip-linux-amd64-asan-clang15 go@d4b0bd28 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 18:43 gotip-linux-amd64-asan-clang15 go@5a0f2a7a crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 18:52 gotip-linux-amd64-asan-clang15 go@53b2b64b crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 19:09 gotip-linux-amd64-asan-clang15 go@80344887 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)

— watchflakes

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "crypto/internal/fips/sha3" && test == "TestAllocations/New"
2024-11-18 19:38 gotip-linux-amd64-asan-clang15 go@bb2a5f05 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 19:54 gotip-linux-amd64-asan-clang15 go@b5906ac4 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 19:57 gotip-linux-amd64-asan-clang15 go@6c660052 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.02s)
2024-11-18 19:59 gotip-linux-amd64-asan-clang15 go@cea365dd crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)

— watchflakes

@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "crypto/internal/fips/sha3" && test == "TestAllocations/New"
2024-11-18 20:29 gotip-linux-amd64-asan-clang15 go@4804d0da crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 20:29 gotip-linux-amd64-asan-clang15 go@e51a33a0 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.01s)
2024-11-18 20:30 gotip-linux-amd64-asan-clang15 go@36b5b053 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 20:30 gotip-linux-amd64-asan-clang15 go@008904ab crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.01s)
2024-11-18 20:30 gotip-linux-amd64-asan-clang15 go@e8c5e6d6 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.05s)
2024-11-18 20:35 gotip-linux-amd64-asan-clang15 go@85fa418f crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 20:35 gotip-linux-amd64-asan-clang15 go@28bac564 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 20:35 gotip-linux-amd64-asan-clang15 go@872031dc crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 20:35 gotip-linux-amd64-asan-clang15 go@700c7b95 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 20:35 gotip-linux-amd64-asan-clang15 go@107e094f crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 20:35 gotip-linux-amd64-asan-clang15 go@083045f9 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.05s)
2024-11-18 20:35 gotip-linux-amd64-asan-clang15 go@e5c4c79c crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.00s)
2024-11-18 20:35 gotip-linux-amd64-asan-clang15 go@5c7b7c7d crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.01s)
2024-11-18 20:35 gotip-linux-amd64-asan-clang15 go@50f18888 crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.01s)
2024-11-18 20:35 gotip-linux-amd64-asan-clang15 go@06e6b8ef crypto/internal/fips/sha3.TestAllocations/New (log) 
=== RUN   TestAllocations/New
    sha3_test.go:383: expected zero allocations, got 2.0
--- FAIL: TestAllocations/New (0.06s)

— watchflakes

@mknyszek
Copy link
Contributor

Fixed by https://go.dev/cl/626438.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Test Flakes
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mknyszek @gopherbot