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
pkg/ccl/testccl/sqlccl/sqlccl_test: TestReadCommittedStmtRetry failed #123661
Comments
Not sure if this is relevant:
|
Looks like it is waiting 41 minutes for the
|
This doesn't appear to be an issue with retries. Rather, the UPDATE statement was blocked from ever completing in the first place. That seems more likely to be an issue outside of SQL. It seems like some latches were held for longer than expected. Perhaps that could prevent the necessary locks from ever being acquired.
There are also 416 latency jump warnings:
It seems like something might have been making this testcluster slow. I'm removing the blocker label, and moving to KV in case they want to investigate why. |
Maybe we should skip this test under race? |
The
The hook seems to be firing before the test expects it to, during the UPDATE to "a". |
123957: sql: deflake TestReadCommittedStmtRetry r=nvanbenschoten a=nvanbenschoten Fixes #123661. This commit deflakes `TestReadCommittedStmtRetry` by not enabling the hook to block writes in the Read Committed transaction until after the first write. This avoids flakiness if the first write is ever retried due to slowness in the cluster, lease instability, or some other reason. Release note: None Co-authored-by: Nathan VanBenschoten <nvanbenschoten@gmail.com>
Fixes #123661. This commit deflakes `TestReadCommittedStmtRetry` by not enabling the hook to block writes in the Read Committed transaction until after the first write. This avoids flakiness if the first write is ever retried due to slowness in the cluster, lease instability, or some other reason. Release note: None
pkg/ccl/testccl/sqlccl/sqlccl_test.TestReadCommittedStmtRetry failed on release-24.1.0-rc @ 34bbed697e77466f52012a80f0f6ae496c0d2889:
Fatal error:
Stack:
Log preceding fatal error
Parameters:
attempt=1
race=true
run=2
shard=3
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-38457
The text was updated successfully, but these errors were encountered: