br: fix the issue that state not set correctly after resolve locks

[3pointer]

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

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tiprow]

Hi @3pointer. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[codecov]

Codecov Report

Merging #46903 (f5197e6) into master (25fd1b7) will decrease coverage by 0.6500%.
Report is 5 commits behind head on master.
The diff coverage is 57.1428%.

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     

Flag	Coverage Δ
integration	27.7927% <0.0000%> (?)
unit	73.3188% <57.1428%> (-0.0404%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	54.0444% <ø> (ø)
parser	85.0019% <ø> (ø)
br	48.7567% <57.1428%> (-4.1508%)	⬇️

[ti-chi-bot]

[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

Needs approval from an approver in each of these files:

• OWNERS [Leavrth,YuJuncen]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-09-12 09:04:49.760207804 +0000 UTC m=+346471.684764200: ☑️ agreed by Leavrth.
• 2023-09-12 09:35:46.728674772 +0000 UTC m=+348328.653231189: ☑️ agreed by YuJuncen.

[3pointer]

/retest

[tiprow]

@3pointer: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #46915.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #46916.