Un-flake 01079_new_range_reader_segfault #48934
Merged
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.
Usage of
rand()
means that the SELECT produces with probability 0.5^20 = 0.000000953 no result. This happend in (*).The query is designed to trigger some specific logic in MergeTreeReader. Rewriting it is not a good idea. I therefore increased the amount of test data to reduce the probability of an empty result significantly. I hope that the same logic as before is triggered.
EDIT: Instead replaced
rand()
by the more deterministicrowNumberInBlock()
.The test currently runs 507 times / day, this means this PR will prevent a failure in ca. 5.6 years from now. Happy 2028!
(*) https://s3.amazonaws.com/clickhouse-test-reports/0/905587b39def432667437efd92c28dde9cc0dfb2/stateless_tests__release__s3_storage__[1/2].html
Changelog category (leave one):