CNDB-16146: Reproduce missing rows failure#2143
Open
michaelsembwever wants to merge 2 commits intomain-5.0from
Open
CNDB-16146: Reproduce missing rows failure#2143michaelsembwever wants to merge 2 commits intomain-5.0from
michaelsembwever wants to merge 2 commits intomain-5.0from
Conversation
Checklist before you submit for review
|
ab46777 to
a290f6e
Compare
|
❌ Build ds-cassandra-pr-gate/PR-2143 rejected by Butler3 regressions found Found 3 new test failures
Found 6 known test failures |
djatnieks
approved these changes
Dec 1, 2025
Member
Author
|
apologies, the plan isn't to commit this, the failure is already covered in The purpose of this PR currently is to have the minimal reproducible for other engineers to investigate/understand. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



What is the issue
https://github.com/riptano/cndb/issues/16146
CC5 UDT test failure.
Not all rows are being returned from the tables with dropped frozen collection/tuple after schema recreation.
Key observations are:
To reproduce