kvnemesis: closed timestamp regressions during test injected reproposals #131450
Labels
branch-master
Failures and bugs on the master branch.
branch-release-23.2
Used to mark GA and release blockers, technical advisories, and bugs for 23.2
branch-release-24.1
Used to mark GA and release blockers, technical advisories, and bugs for 24.1
branch-release-24.2
Used to mark GA and release blockers, technical advisories, and bugs for 24.2
branch-release-24.3
Used to mark GA and release blockers, technical advisories, and bugs for 24.3
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
C-test-failure
Broken test (automatically or manually discovered).
P-2
Issues/test failures with a fix SLA of 3 months
T-kv
KV Team
Describe the problem
We've seen KVNemesis routinely fail due to closed timestamp regressions. For example: #118471 (comment)
We attempted to fix this in #121965. However, we still see this sometimes. @pav-kv has a theory about why: #118471 (comment).
Jira issue: CRDB-42546
Epic CRDB-37617
Note to L2 triagers: if you encounter an instance of this failure during triage, point to this issue and close the test flake with the
X-duplicate
label.The text was updated successfully, but these errors were encountered: