-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
sql/sem/builtins: TestSerialNormalizationWithUniqueUnorderedID failed [deadlock in handleRaftReady] #115541
Comments
sql/sem/builtins.TestSerialNormalizationWithUniqueUnorderedID failed with artifacts on master @ 8bcaae9db5fe148536a24c2b0b99ef6691687ebc:
Parameters: |
Might relate to the potential deadlock in #115542 |
This isn't an actual deadlock -- the test is just slow. It takes ~30 or so seconds to run normally. The addition of test-only verification in the lock table made this test susceptible to hitting timeouts when running under a deadlock build, which is why we're seeing these failures pop up. Given it's already skipped under race, I'm going to skip this under deadlock as well. |
115685: builtins: skip TestSerialNormalizationWithUniqueUnorderedID under deadlock r=erikgrinaker a=arulajmani This test is extremely slow -- it takes ~30s to run normally. The addition of test-only verification pushed it over the edge, such that running it under the deadlock detector would cause spurious failures, so we skip it. Closes #115541 Release note: None Co-authored-by: Arul Ajmani <[email protected]>
…dlock This test is extremely slow -- it takes ~30s to run normally. The addition of test-only verification pushed it over the edge, such that running it under the deadlock detector would cause spurious failures, so we skip it. Closes #115541 Release note: None
sql/sem/builtins.TestSerialNormalizationWithUniqueUnorderedID failed with artifacts on master @ b95ad1dc5d1c00ab1b99a13cfd5014c1093bef89:
Parameters:
TAGS=bazel,gss,deadlock
,stress=true
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-34090
The text was updated successfully, but these errors were encountered: