-
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
test(DM): add check log contain to safe-mode
integration test
#7152
Conversation
[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. |
/run-dm-integration-test |
/area dm |
@okJiang: once the present PR merges, I will cherry-pick it on top of release-6.3 in the new PR and assign it to you. In response to this:
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. |
dm/tests/safe_mode/run.sh
Outdated
@@ -206,6 +206,9 @@ function safe_mode_duration() { | |||
dmctl_operate_source create $WORK_DIR/source2.yaml $SOURCE_ID2 | |||
|
|||
dmctl_start_task "$cur/conf/dm-task-safe-mode-duration.yaml" "--remove-meta" | |||
# Worker1 need to start relay, so it is slow. | |||
# It is possible that worker1 has not loaded before check diff. | |||
sleep 3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think sleep can make it stable, you may use check_log_contains_with_retry to make sure test enter a centain state.
/type cherry-pick-for-release-6.3 |
…ter to sync status, and complete one dml
/run-dm-integration-test |
dm/tests/safe_mode/run.sh
Outdated
@@ -211,6 +211,8 @@ function safe_mode_duration() { | |||
run_sql_file $cur/data/db1.increment.sql $MYSQL_HOST1 $MYSQL_PORT1 $MYSQL_PASSWORD1 | |||
run_sql_file $cur/data/db2.increment.sql $MYSQL_HOST2 $MYSQL_PORT2 $MYSQL_PASSWORD2 | |||
|
|||
# make sure worker1 enter to sync status, and complete one dml | |||
check_log_contain_with_retry "alter table t1 add column age int" $WORK_DIR/worker1/log/dm-worker.log |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code change doesn't match the PR title. So which one should be changed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is working in progress. I will update it
safe-mode
integration testsafe-mode
integration test
/run-dm-integration-test |
/cc @GMHDBJD @lance6716 |
/run-all-tests |
safe-mode
integration testsafe-mode
integration test
/run-check-issue-triage-complete |
1 similar comment
/run-check-issue-triage-complete |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-verify |
/merge |
@okJiang: In response to this:
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. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 97981a0
|
/lable needs-cherry-pick-release-6.3 |
/check-issue-triage-complete |
@okJiang: 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. |
/remove-type cherry-pick-for-release-6.3 |
/run-verify |
/run-engine-integration-test |
1 similar comment
/run-engine-integration-test |
In response to a cherrypick label: new pull request created: #7163. |
What problem does this PR solve?
Issue Number: ref #4159, close #7099
What is changed and how it works?
Check 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