Skip to content
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

kvnemesis: closed timestamp regressions during test injected reproposals #131450

Open
arulajmani opened this issue Sep 26, 2024 · 1 comment · May be fixed by #139343 or #139350
Open

kvnemesis: closed timestamp regressions during test injected reproposals #131450

arulajmani opened this issue Sep 26, 2024 · 1 comment · May be fixed by #139343 or #139350
Assignees
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

Comments

@arulajmani
Copy link
Collaborator

arulajmani commented Sep 26, 2024

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.

@arulajmani arulajmani added 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 labels Sep 26, 2024
Copy link

blathers-crl bot commented Sep 26, 2024

Hi @arulajmani, please add branch-* labels to identify which branch(es) this C-bug affects.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@rimadeodhar rimadeodhar added the T-kv KV Team label Dec 26, 2024
@nicktrav nicktrav added branch-master Failures and bugs on the master branch. branch-release-24.1 Used to mark GA and release blockers, technical advisories, and bugs for 24.1 branch-release-23.2 Used to mark GA and release blockers, technical advisories, and bugs for 23.2 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 labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
4 participants