Fix flaky test in test_merge_tree_s3 and others with retry_attempts=0#93564
Merged
Fix flaky test in test_merge_tree_s3 and others with retry_attempts=0#93564
Conversation
Contributor
|
Workflow [PR], commit [f88fea5] Summary: ❌
|
CheSema
reviewed
Jan 8, 2026
Member
There was a problem hiding this comment.
I do not think that this would fix flakiness.
It flaks due to
<retry_attempts>0</retry_attempts>
in the storages broken_s3, broken_s3_always_multi_part and s3 function broken_s3.
Even without fault ejection any queries to such storages could emit errors.
I think it is impossible to have a reliable test with retry_attempts=0 in our CI. That tests have to be rewritten completely.
Member
|
I will add here few changes. |
Member
Author
|
@CheSema : As author of PR, I am not able to approve it. Please approve and merge |
CheSema
approved these changes
Jan 12, 2026
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.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
resolves #92909
Documentation entry for user-facing changes