-
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 #106829
Comments
cc @andyyang890 I wonder if the latest change to increase the number of samples makes this more likely to timeout. If so, we can raise the timeout in the BUILD.bazel file. |
Noting for the record that I am able to reproduce this under stress and it looks like the query here gets stuck/times out sometimes: cockroach/pkg/sql/sem/builtins/builtins_test.go Lines 147 to 164 in 4b0eb97
Still digging into the root cause for this. |
Some observations from the logs below, not sure if any of these are significant. In the test logs, I see a bunch of messages like this initially, but then they stop showing up for the last few minutes before the test times out:
Throughout the logs, there are also a lot of messages like these:
Pure speculation but could the stats collection be taking a very long time/hanging? |
I don't see anything else that stands out in the logs and setting Here's the test log for the failure (which includes a stack dump) after I was able to get it to fail under stress: |
Why would this test need more than 5 minutes? It passes in a few seconds when I run it.
How do you know this query is timing out? |
From the stack dump, this is one of the stuck goroutines:
Specifically this part of the stack trace (the line number is slightly different from master since I added a little bit of debugging code, but it reproduces under stress without the debugging code too):
Maybe I'm interpreting what this means wrong, but I think it means this query has been running/stuck for 4 minutes? |
I think your interpretation is correct - the query is running for at least 4 minutes. I don't think it's expected - locally for me it ran under 100ms. I'll investigate. |
sql/sem/builtins.TestSerialNormalizationWithUniqueUnorderedID failed with artifacts on master @ 334e261af905918edf3ffe43e07f724e9f9b0b01:
Fatal error:
Stack:
Log preceding fatal error
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-29733
The text was updated successfully, but these errors were encountered: