test(dm): fix using pgrep to check argument pattern (#6572) #6584
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated cherry-pick of #6572
Signed-off-by: lance6716 lance6716@gmail.com
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