-
Notifications
You must be signed in to change notification settings - Fork 288
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
makefile(all): add new cases to run_group and check cases in makefile #8794
makefile(all): add new cases to run_group and check cases in makefile #8794
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. |
Skipping CI for Draft Pull Request. |
a4170f0
to
df8560f
Compare
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.
Thanks!
check_dm_integration_test: | ||
./dm/tests/run_group.sh "check others" | ||
|
||
check_cdc_integration_test: | ||
./tests/integration_tests/run_group.sh check "others" |
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.
Why don't we unify it to "check others"
or check "others"
?
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.
Because ./tests/integration_tests/run_group.sh
and ./dm/tests/run_group.sh
have a different number of parameters.
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 meat does there is any possibility to change it and unify it. It is quite confusing to have two style scripts in the same project.
If you think it is time-consuming, this should not be a blocker. 😆
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 main reason is that there are ci scripting issues involved here. No matter how you change it, there will always be inconsistent behavior, either inside the script or inside the makefile.
/retest |
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.
Nice to improve it, but not a blocker.
/retest |
This pull request has been accepted and is ready to merge. Commit hash: 08d1f7a
|
/test all |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 7fdbc25
|
/test all |
@CharlesCheung96: 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. |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created to branch |
What problem does this PR solve?
Issue Number: ref #8772
What is changed and how it works?
make check
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