-
Notifications
You must be signed in to change notification settings - Fork 476
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
race detector makes TestGenerateKey flaky in pkg/server/plugin/keymanager/awskms #2714
Labels
help wanted
Issues with this label are ready to start work but are in need of someone to do it
Comments
I can no longer reproduce this flakiness. I can make it fail by exceeding the goroutine limit in the race detector (which in turn is a limit in LLVM. See golang/go#38184):
|
This failed in a different way for me in a CI run with race detection enabled:
Reopening the issue since this test still seems to be racy. |
rturner3
added
the
help wanted
Issues with this label are ready to start work but are in need of someone to do it
label
Mar 15, 2022
azdagron
added a commit
to azdagron/spire
that referenced
this issue
Mar 16, 2022
Also fixes a bug in the AssertLogsContainEntries that did not normalize the log entry data fields. Fixes: spiffe#2714 Signed-off-by: Andrew Harding <aharding@vmware.com>
azdagron
added a commit
that referenced
this issue
Mar 16, 2022
Also fixes a bug in the AssertLogsContainEntries that did not normalize the log entry data fields. Fixes: #2714 Signed-off-by: Andrew Harding <aharding@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
help wanted
Issues with this label are ready to start work but are in need of someone to do it
Linux [redacted] 5.4.129+ #1 SMP Wed Aug 18 19:58:18 PDT 2021 x86_64 GNU/Linux
The
TestGenerateKey
inpkg/server/plugin/keymanager/awskms
fails at an unacceptable rate when run under the race detector. No specific data race is detected, but the additional overhead of enabling the race detector seems to trigger failures in some time-dependent tests. It tends to fail in a few ways:Example 1:
Example 2:
These do not occur when race detector is not enabled:
The text was updated successfully, but these errors were encountered: