-
Notifications
You must be signed in to change notification settings - Fork 720
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
*: move out replication and syncer #6418
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. |
c352e30
to
b150f05
Compare
b150f05
to
d0a5674
Compare
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## master #6418 +/- ##
==========================================
- Coverage 74.74% 74.60% -0.14%
==========================================
Files 414 414
Lines 42352 42352
==========================================
- Hits 31655 31597 -58
- Misses 7915 7964 +49
- Partials 2782 2791 +9
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
Signed-off-by: Ryan Leung <rleungx@gmail.com>
d0a5674
to
78f8c95
Compare
@@ -151,7 +151,7 @@ func TestRegionSyncer(t *testing.T) { | |||
re.Equal(region.GetLeader(), r.GetLeader()) | |||
re.Equal(region.GetBuckets(), r.GetBuckets()) | |||
} | |||
re.NoError(failpoint.Disable("github.com/tikv/pd/server/syncer/noFastExitSync")) |
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.
This issue may not be related to this PR change. The old path github.com/tikv/pd/server/syncer/noFastExitSync
seems to be wrong? Should be regionsyncer
other than syncer
. So does this failpoint work?
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 package name is syncer
I think.
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.
Get
/merge |
@rleungx: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests 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. |
This pull request has been accepted and is ready to merge. Commit hash: 78f8c95
|
@rleungx: Your PR was out of date, I have automatically updated it for you. 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. |
ref tikv#5839 Signed-off-by: Ryan Leung <rleungx@gmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
What problem does this PR solve?
Issue Number: Ref #5839.
What is changed and how does it work?
This PR mainly did the following changes:
Once we reach an agreement, I will try to split this PR into pieces.
Most of the jobs are done in the previous PRs. This PR will only move some packages out of server.
Check List
Tests
Release note