-
Notifications
You must be signed in to change notification settings - Fork 286
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
chaos: fix utf8mb3 and utf8mb4_0900_ai_ci for chaos test #6960
Conversation
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## master #6960 +/- ##
================================================
+ Coverage 59.8253% 59.8591% +0.0337%
================================================
Files 791 790 -1
Lines 90221 90561 +340
================================================
+ Hits 53975 54209 +234
- Misses 31498 31592 +94
- Partials 4748 4760 +12 |
/hold |
https://github.com/pingcap/tiflow/actions/runs/2997517629 chaos test passed. cc @lance6716 @D3Hunter @buchuitoudegou |
/unhold |
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: bb64a8e
|
/merge |
/run-verify |
@GMHDBJD: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/run-dm-integration-test |
What problem does this PR solve?
Issue Number: ref #4159
What is changed and how it works?
Release note