-
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/kvserver: TestProtectedTimestamps failed #93497
Comments
Saw an instance of this on master as well in #93673. |
22.1 issue: #93183. |
We have marked this test failure issue as stale because it has been |
Just picked this up, fails now with
|
kv/kvserver.TestProtectedTimestamps failed with artifacts on release-22.2 @ 8a2050b00bac7e247df26c63aa0c8c1ca4fd7996:
Parameters: Same failure on other branches
|
105383: concurrency: split out replicated/unreplicated lock holder information r=nvanbenschoten a=arulajmani The MVCC keyspace is the source of truth for replicated locks. We've previously concluded that trying to keep the in-memory state of replicated locks in sync is fraught with subtle issues. We instead do the dumb thing and forget replicated locks in a few places (see comment about mvccResolveWriteIntent in tryUpdateLockLocked). It follows that we don't need to track as much information about replicated locks (like we do for unreplicated locks). For example, we do not need to track the sequence number history for replicated locks. This patch splits out lock holder information about replicated locks and unreplicated locks into 2 different structs. As mentioned above, we no longer track seqeunce numbers for the former. Informs #102270 Release note: None 105641: kvserver: deflake TestProtectedTimestamps r=irfansharif a=arulajmani This patch fixes a few (hopefully all) issues with TestProtectedTimestamps. In particular, - The range max bytes used by the test was broken after the lower bound was bumped in a37e053. We up the value. - There was flakiness at various points in the test as a result of lease transfers. We change the test to run on a single node test cluster to get around this. Fixes: #93497 Release note: None Co-authored-by: Arul Ajmani <[email protected]>
This patch fixes a few (hopefully all) issues with TestProtectedTimestamps. In particular, - The range max bytes used by the test was broken after the lower bound was bumped in a37e053. We up the value. - There was flakiness at various points in the test as a result of lease transfers. We change the test to run on a single node test cluster to get around this. Fixes: #93497 Release note: None
This patch fixes a few (hopefully all) issues with TestProtectedTimestamps. In particular, - The range max bytes used by the test was broken after the lower bound was bumped in a37e053. We up the value. - There was flakiness at various points in the test as a result of lease transfers. We change the test to run on a single node test cluster to get around this. Fixes: #93497 Release note: None
This patch fixes a few (hopefully all) issues with TestProtectedTimestamps. In particular, - The range max bytes used by the test was broken after the lower bound was bumped in a37e053. We up the value. - There was flakiness at various points in the test as a result of lease transfers. We change the test to run on a single node test cluster to get around this. Fixes: #93497 Release note: None
kv/kvserver.TestProtectedTimestamps failed with artifacts on release-22.2 @ 9a14474ed902e168ec6e6d1ea586d13eb92a2288:
Parameters:
TAGS=bazel,gss
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-22365
The text was updated successfully, but these errors were encountered: