-
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
storage: More CheckSSTConflicts fixes #98519
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Should we re-enable range keys in kvnemesis here too? See #98475.
A few additional fixes around CheckSSTConflicts, stats calculations, and Next()ing logic, caught by kvnemesis. Hopefully the last of its kind. Also re-enable kvnemesis testing for range keys in AddSSTable, reverting cockroachdb#98475. Fixes cockroachdb#94141. Fixes cockroachdb#98473. Informs cockroachdb#94876. Epic: none Release note: None
34bffa5
to
9ec7760
Compare
@erikgrinaker TFTR! And yep, I've re-enabled it in the latest push. |
TFTR! bors r=erikgrinaker |
Build failed (retrying...): |
Build failed (retrying...): |
This PR was included in a batch that was canceled, it will be automatically retried |
Build failed (retrying...): |
Build failed: |
Timeout in UI tests. bors r=erikgrinaker |
Build failed (retrying...): |
Build succeeded: |
A few additional fixes around CheckSSTConflicts, stats calculations, and Next()ing logic, caught by kvnemesis. Hopefully the last of its kind.
Also re-enable kvnemesis testing for range keys in AddSSTable, reverting #98475.
Fixes #94141.
Fixes #98473.
Informs #94876.
Epic: none
Release note: None