br: use atomic.Pointer instead of atomic.Value

[yoshikipom]

What problem does this PR solve?

Issue Number: ref #44736

Problem Summary:

What changed and how does it work?

Check List

Tests

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

  Current Tests have already covered, so no need to add more tests.

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]

Hi @yoshikipom. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

[tiprow]

Hi @yoshikipom. 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.

[lance6716]

/ok-to-test

[codecov]

Codecov Report

Merging #49359 (4d2100b) into master (9322568) will increase coverage by 1.8421%.
Report is 3 commits behind head on master.
The diff coverage is 0.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #49359        +/-   ##
================================================
+ Coverage   71.0517%   72.8938%   +1.8421%     
================================================
  Files          1368       1415        +47     
  Lines        401578     416972     +15394     
================================================
+ Hits         285328     303947     +18619     
+ Misses        96418      93862      -2556     
+ Partials      19832      19163       -669     

Flag	Coverage Δ
integration	47.2149% <0.0000%> (?)
unit	71.0515% <ø> (-0.0002%)	⬇️

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

Components	Coverage Δ
dumpling	53.9663% <ø> (ø)
parser	∅ <ø> (∅)
br	56.1270% <0.0000%> (+3.2335%)	⬆️

[lance6716]

Thanks for your contribution, and please check CI link to update the test cases

[lance6716]

/test pull-lightning-integration-test

[tiprow]

@lance6716: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test tiprow_fast_test

Use /test all to run all jobs.

In response to this:

/test pull-lightning-integration-test

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.

[lance6716]

don't worry, ci seems failed by other problems. I'll check it tomorrow

[yoshikipom]

@lance6716 Thank you for your support!

[lance6716]

Hi @yoshikipom please merge master branch, integration tests should be okay now

[lance6716]

/test pull-lightning-integration-test

[tiprow]

@lance6716: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test tiprow_fast_test

Use /test all to run all jobs.

In response to this:

/test pull-lightning-integration-test

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.

[lance6716]

/cc @YuJuncen @Leavrth

[3pointer]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, lance6716

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:

• br/OWNERS [3pointer]

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-12-13 01:44:56.621774323 +0000 UTC m=+406987.659001248: ☑️ agreed by lance6716.
• 2023-12-13 07:12:09.441522198 +0000 UTC m=+426620.478749126: ☑️ agreed by 3pointer.