br: fix backoffer can't handle multierrs

[RidRisR]

What problem does this PR solve?

Issue Number: close #54053

Problem Summary:

Backoffer can't recognize multierrs, therefore it would stop retry for recursive retry calling

What changed and how does it work?

Enable backoffer to recognize the multierr, and it will only check the last err returned

Check List

Tests

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

  • I checked and no code files have been changed.

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

[tiprow]

Hi @RidRisR. 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-sigs/prow repository.

[BornChanger]

/hold

[codecov]

Codecov Report

Attention: Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 55.9839%. Comparing base (9008d23) to head (79ca74a).
Report is 9 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #54084         +/-   ##
=================================================
- Coverage   72.8351%   55.9839%   -16.8512%     
=================================================
  Files          1516       1636        +120     
  Lines        434738     608081     +173343     
=================================================
+ Hits         316642     340428      +23786     
- Misses        98508     244018     +145510     
- Partials      19588      23635       +4047     

Flag	Coverage Δ
integration	22.9500% <80.0000%> (?)

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

Components	Coverage Δ
dumpling	52.9656% <ø> (ø)
parser	∅ <ø> (∅)
br	62.8620% <80.0000%> (+16.7360%)	⬆️

[YuJuncen]

rest lgtm

[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:

• br/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:

• 2024-06-18 06:53:53.312216309 +0000 UTC m=+97759.797705139: ☑️ agreed by Leavrth.
• 2024-06-19 06:22:01.204791514 +0000 UTC m=+182247.690280348: ☑️ agreed by YuJuncen.

[hawkingrei]

/retest

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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