-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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/kvnemesis: TestKVNemesisSingleNode_ReproposalChaos failed #115598
Comments
@arulajmani Related to the recent lock table assertions you've added? |
kv/kvnemesis.TestKVNemesisSingleNode_ReproposalChaos failed with artifacts on release-23.2 @ df4b4e856c33477cdad4a659adba959987c488ca:
Parameters: |
Yeah, this looks related to the verification I added. Looking into this, but I'll re-label this as a GA-blocker given we're only seeing this with shared locks. |
I have a plausible explanation for what might be going on here. In both these cases, we see the panic is coming from a lock held by a finalized transaction. For example,
Note that the shared lock held by txn That would explain why req 457 is waiting on this key. Once txn This isn't really a correctness issue, even though we're tripping verification here. To that end, I'll remove the GA-blocker label. I'm not sure what the best fix should be here yet. [1] If it were a transactional request, we'd expect it to still be in the lock's wait queue as an inactive waiter. |
kv/kvnemesis.TestKVNemesisSingleNode_ReproposalChaos failed with artifacts on release-23.2 @ 75dbd5b7dd05e885fd729e3bb13622c8f8b74b85: Fatal error:
Stack:
Log preceding fatal error
Parameters: |
kv/kvnemesis.TestKVNemesisSingleNode_ReproposalChaos failed with artifacts on release-23.2 @ 43a2532550ca7abfc3c5682df31b0cc20da934b0:
Parameters: |
kv/kvnemesis.TestKVNemesisSingleNode_ReproposalChaos failed with artifacts on release-23.2 @ caaa842c957d8487be32504cdd6379745f1a3ff6: Fatal error:
Stack:
Log preceding fatal error
Parameters: |
We've seen KVNemesis fail regularly because of a specific validation error. For now, quieten the assertion until the issue is fixed -- this ensures legit bugs aren't drowned out by the noise. Informs cockroachdb#115694 Informs cockroachdb#115598 Release note: None
116090: serverccl: skip data distribution test under race r=maryliag a=dhartunian Resolves: #115932 Epic: None Release note: None 116125: sql: skip a couple of tests under deadlock r=yuzefovich a=yuzefovich `TestExplainRedact` and `TestExplainRedactDDL` are quite long, making that some KV level deadlock mechanism fires incorrectly. We've skipped other tests due to this, so this commit skips these two as well. Fixes: #115861. Fixes: #115998. Release note: None 116242: concurrency: quieten KVNemesis failure because of validation r=arulajmani a=arulajmani We've seen KVNemesis fail regularly because of a specific validation error. For now, quieten the assertion until the issue is fixed -- this ensures legit bugs aren't drowned out by the noise. Informs #115694 Informs #115598 Release note: None Co-authored-by: David Hartunian <[email protected]> Co-authored-by: Yahor Yuzefovich <[email protected]> Co-authored-by: Arul Ajmani <[email protected]>
kv/kvnemesis.TestKVNemesisSingleNode_ReproposalChaos failed with artifacts on release-23.2 @ bc665a398d2ddbd27b60119e8272f49d0abf78a2:
Parameters: Same failure on other branches
|
We have marked this test failure issue as stale because it has been |
kv/kvnemesis.TestKVNemesisSingleNode_ReproposalChaos failed with artifacts on release-23.2 @ 84f0e5f4625f8a2155d531251e0df6db8a5ef053: Fatal error:
Stack:
Log preceding fatal error
Parameters:
|
We have marked this test failure issue as stale because it has been |
kv/kvnemesis.TestKVNemesisSingleNode_ReproposalChaos failed with artifacts on release-23.2 @ df4b4e856c33477cdad4a659adba959987c488ca:
Fatal error:
Stack:
Log preceding fatal error
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-34118
The text was updated successfully, but these errors were encountered: