-
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
kv/kvserver: TestDiscoverIntentAcrossLeaseTransferAwayAndBack failed #122102
Comments
The test is stuck here on the
The test's main goroutine who should eventually close the channel is blocked on latches:
The latches are likely held by the first goroutine, which would create a deadlock and explain the timeout. But why doesn't this usually deadlock? These are two We do see a lease request (must be a
|
This is interesting that it is failing. I had a problem understanding why this was failing and and removed it from the new proxy behavior in my PR here: #121273 because it was hitting the same issue and I couldn't figure out how to address it. So there is at least a way to make this failure happen much more easily, but I'm not sure I understand exactly why this is failing or if this has become more common in 24.1 due to some changes made. I'm not going to have time this week to look at this failure, but it would be good to understand it better and to remove the TODO from the linked PR once this is fixed. |
We have marked this test failure issue as stale because it has been |
kv/kvserver.TestDiscoverIntentAcrossLeaseTransferAwayAndBack failed on release-24.1 @ 87740bd080658e93b40637556c9dfa27a91f8cf5:
Fatal error:
Stack:
Log preceding fatal error
Parameters:
attempt=1
race=true
run=3
shard=16
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-37704
The text was updated successfully, but these errors were encountered: