-
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
tests(ticdc): add lossy_ddl test #8859
tests(ticdc): add lossy_ddl test #8859
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. |
tests/integration_tests/run_group.sh
Outdated
@@ -40,7 +40,7 @@ groups=( | |||
["G22"]='big_txn csv_storage_basic changefeed_finish sink_hang canal_json_storage_basic' | |||
["G23"]='multi_topics new_ci_collation_with_old_value batch_add_table multi_changefeed' | |||
["G24"]='consistent_replicate_nfs consistent_replicate_ddl owner_resign api_v2' | |||
["G25"]='canal_json_storage_partition_table csv_storage_partition_table csv_storage_multi_tables_ddl' | |||
["G25"]='canal_json_storage_partition_table csv_storage_partition_table csv_storage_multi_tables_ddl lossy_ddl' |
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.
Only for temporarily testing it. Add a new group before merging it.
/test all |
Blocked by #8685 |
Tested locally: docker-compose-mysql_integration_test-1 | run task successfully
docker-compose-mysql_integration_test-1 | wait process cdc.test exit for 1-th time...
docker-compose-mysql_integration_test-1 | wait process cdc.test exit for 2-th time...
docker-compose-mysql_integration_test-1 | wait process cdc.test exit for 3-th time...
docker-compose-mysql_integration_test-1 | wait process cdc.test exit for 4-th time...
docker-compose-mysql_integration_test-1 | cdc.test: no process found
docker-compose-mysql_integration_test-1 | wait process cdc.test exit for 5-th time...
docker-compose-mysql_integration_test-1 | process cdc.test already exit
docker-compose-mysql_integration_test-1 | [Wed Apr 26 08:53:10 UTC 2023] <<<<<< run test case lossy_ddl success! >>>>>>
docker-compose-mysql_integration_test-1 | \033[0;36m<<< Run all test success >>>\033[0m
|
/test all |
function run() { | ||
# Use blackhole sink to check if the DDL is lossy. | ||
# So no need to run this test for other sinks. | ||
if [ "$SINK_TYPE" != "mysql" ]; then |
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.
Better to run this in kafka or cloudstorage pipeline since mysql pipeline is currently under heavy load.
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.
Cool! I will change it.
f400b12
to
984351b
Compare
/test all |
This pull request has been accepted and is ready to merge. Commit hash: 1fad4bf
|
/test all |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: fcffd00
|
/test all |
@hi-rustin: 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. |
/test all |
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
close pingcap#8686 Signed-off-by: hi-rustin <rustin.liu@gmail.com>
What problem does this PR solve?
Issue Number: close #8686
What is changed and how it works?
Add test for lossy DDLs.
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
No
Do you need to update user documentation, design documentation or monitoring documentation?
No
Release note