-
Notifications
You must be signed in to change notification settings - Fork 289
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
latency(cdc): 2 phase scheduling processor bug fix #5728
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. |
Test TestTableExecutorAddingTableDirectly fails. |
|
||
revision, err := etcdClient.GetOwnerRevision(etcdCliCtx, captureID) | ||
revision, err := etcdClient.GetOwnerRevision(etcdCliCtx, ownerCaptureID) |
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.
Any test covers it?
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.
no, a mock etcd client is expected.
/run-unit-test |
* fix by suggestion, use unique state for the table. * fix TestTableExecutorAddingTableDirectly * add ut TestTableExecutorAddingTableIndirectly * add ut TestTableExecutorAddingTableIndirectly
* fix by suggestion, use unique state for the table. * fix TestTableExecutorAddingTableDirectly * add ut TestTableExecutorAddingTableIndirectly * add ut TestTableExecutorAddingTableIndirectly
* fix by suggestion, use unique state for the table. * fix TestTableExecutorAddingTableDirectly * add ut TestTableExecutorAddingTableIndirectly * add ut TestTableExecutorAddingTableIndirectly
* fix by suggestion, use unique state for the table. * fix TestTableExecutorAddingTableDirectly * add ut TestTableExecutorAddingTableIndirectly * add ut TestTableExecutorAddingTableIndirectly
* fix by suggestion, use unique state for the table. * fix TestTableExecutorAddingTableDirectly * add ut TestTableExecutorAddingTableIndirectly * add ut TestTableExecutorAddingTableIndirectly
* fix by suggestion, use unique state for the table. * fix TestTableExecutorAddingTableDirectly * add ut TestTableExecutorAddingTableIndirectly * add ut TestTableExecutorAddingTableIndirectly
* fix by suggestion, use unique state for the table. * fix TestTableExecutorAddingTableDirectly * add ut TestTableExecutorAddingTableIndirectly * add ut TestTableExecutorAddingTableIndirectly
* fix by suggestion, use unique state for the table. * fix TestTableExecutorAddingTableDirectly * add ut TestTableExecutorAddingTableIndirectly * add ut TestTableExecutorAddingTableIndirectly
* fix by suggestion, use unique state for the table. * fix TestTableExecutorAddingTableDirectly * add ut TestTableExecutorAddingTableIndirectly * add ut TestTableExecutorAddingTableIndirectly
What problem does this PR solve?
Issue Number: ref #4757
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