test: add a case of Mariadb for dm_upstream_switch #10735
Conversation
***Update Dockerfile for mysql image in upstream_switch*** ***Remove unnecessary lines in Dockerfile for upstream_switch_mariadb
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ti-chi-bot
bot
added
release-note-none
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## master #10735 +/- ##
================================================
+ Coverage 57.5412% 57.5465% +0.0053%
================================================
Files 850 851 +1
Lines 126770 126793 +23
================================================
+ Hits 72945 72965 +20
Misses 48384 48384
- Partials 5441 5444 +3 |
|
/retest |
| - name: Slack notification | ||
| if: ${{ failure() }} | ||
| env: | ||
| SLACK_WEBHOOK: ${{ secrets.SLACK_NOTIFY }} |
There was a problem hiding this comment.
no one use slack now, could we use feishu instead
| @@ -0,0 +1,25 @@ | |||
| vrrp_script chk_mysql_port { | |||
There was a problem hiding this comment.
the folder name need change
Solving this problem #10741 later may require modifying the case. If there is no need to modify it, I will merge it together. |
|
/retest |
What problem does this PR solve?
Issue Number: close #10734, close #10733
What is changed and how it works?
gtid_domain_idgtid_strict_modemaster_use_gtid=slave_posCheck List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note