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

branch-2.1: [test](move-memtable) mitigate flaky injection test skip_two_backends #47082 #47111

Merged
merged 1 commit into from
Jan 17, 2025

Conversation

github-actions[bot]
Copy link
Contributor

Cherry-picked from #47082

…s` (#47082)

Mitigate flaky test `skip_two_backends` in
test_multi_replica_fault_injection.

This test assumes a 3 BE environment and injects failure to 2 of them.
However, it is currently running in a 4 BE environment. Depending on the
replica distribution, the results may vary.
This PR addresses the issue by acknowledging an additional error
message. However, certain tablet distributions could still cause the
test to be flaky, particularly as the number of backends increases.
@hello-stephen
Copy link
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring reopened this Jan 16, 2025
@hello-stephen
Copy link
Contributor

run buildall

@yiguolei yiguolei merged commit 43bfca9 into branch-2.1 Jan 17, 2025
19 checks passed
@github-actions github-actions bot deleted the auto-pick-47082-branch-2.1 branch January 17, 2025 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants