-
Notifications
You must be signed in to change notification settings - Fork 287
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): fix using pgrep to check argument pattern (#6572) #6585
test(dm): fix using pgrep to check argument pattern (#6572) #6585
Conversation
Signed-off-by: ti-chi-bot <[email protected]>
[REVIEW NOTIFICATION] This pull request has not been approved. 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: 99408aa
|
/merge |
This pull request has been accepted and is ready to merge. Commit hash: dd24db3
|
/merge |
This is an automated cherry-pick of #6572
Signed-off-by: lance6716 [email protected]
What problem does this PR solve?
Issue Number: close #6526, close #5731, close #5287
What is changed and how it works?
kill_process dm-worker1
in test script, and finally it will becomepgrep dm-worker1
. This is not right becausedm-worker1
is in arguments andpgrep
only check process name.shardddl
.tb
ADD COLUMNnew_col1
INT DEFAULT -1 #5807Check 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