-
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/logictest: failure: use of Span after Finish #83739
Comments
sql/logictest.TestLogic failed with artifacts on master @ 3c9b17113488d2ee6929936aa6ec48396f3ed71c:
Same failure on other branches
|
Check artifacts to see if it's a timeout? If so, close as a dup of some issues that @yuzefovich opened. |
sql/logictest.TestLogic failed with artifacts on master @ 33d70998719051ee058bc9e516afa238ea7b7451:
Same failure on other branches
|
sql/logictest.TestLogic failed with artifacts on master @ 03d5260a467b8640de41ee08054c1ce05f91966c:
Same failure on other branches
|
I don't see anything in the artifacts that indicates a timeout, but it seems likely given that this test sometimes hangs for minutes at a time when I stress it, but other times completes several iterations in a 5 second period:
|
|
sql/logictest.TestLogic failed with artifacts on master @ 54b4fcaa231abd16260fb09722ed291dbd6a4900:
Same failure on other branches
|
Thanks for tracking that stacktrace down @ajwerner! ❤️ |
The next step may be to run stress logictest with -v -show-sql , which prints the queries and disables parallelism. Should help identify the query. May take 24 hours or so to reproduce it. |
I think it's crucial that it fails only with |
sql/logictest.TestLogic failed with artifacts on master @ 4e8134033890c956d39020f28a0e99b21b32649f:
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-17229
The text was updated successfully, but these errors were encountered: