br: fix the issue that state not set correctly after resolve locks#46903
br: fix the issue that state not set correctly after resolve locks#46903ti-chi-bot[bot] merged 2 commits intopingcap:masterfrom
Conversation
|
Skipping CI for Draft Pull Request. |
|
Hi @3pointer. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. DetailsInstructions 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 kubernetes/test-infra repository. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #46903 +/- ##
================================================
- Coverage 73.3592% 72.7092% -0.6500%
================================================
Files 1328 1350 +22
Lines 397004 404372 +7368
================================================
+ Hits 291239 294016 +2777
- Misses 87174 91753 +4579
- Partials 18591 18603 +12
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Leavrth, YuJuncen The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
@3pointer: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
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 kubernetes/test-infra repository. |
|
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>
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io> Conflicts: br/pkg/streamhelper/advancer.go br/pkg/streamhelper/advancer_test.go
What problem does this PR solve?
Issue Number: ref #40759
Problem Summary:
After PR #45904 merged. advancer resolve lock state set is too frequently. This PR try to correct it.
What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.