br: avoid wrong warning

[Leavrth]

What problem does this PR solve?

Issue Number: close #55902

Problem Summary:
the wrong warning log is print after backup done.

What changed and how does it work?

don't print the wrong warning log.

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 @Leavrth. 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.7252%. Comparing base (df821b9) to head (863231b).
Report is 436 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #56492         +/-   ##
=================================================
- Coverage   73.2357%   57.7252%   -15.5105%     
=================================================
  Files          1626       1773        +147     
  Lines        448692     645492     +196800     
=================================================
+ Hits         328603     372612      +44009     
- Misses        99977     247953     +147976     
- Partials      20112      24927       +4815     

Flag	Coverage Δ
integration	40.2763% <0.0000%> (?)
unit	72.8887% <100.0000%> (+0.4486%)	⬆️

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

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	64.0504% <100.0000%> (+18.5789%)	⬆️

[Leavrth]

/retest

[tiprow]

@Leavrth: 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-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, 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 [3pointer,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-10-10 06:11:09.97046209 +0000 UTC m=+1112825.390675099: ☑️ agreed by 3pointer.
• 2024-10-10 06:12:27.631817619 +0000 UTC m=+1112903.052030628: ☑️ agreed by YuJuncen.

[Leavrth]

/ok-to-test

[Leavrth]

/retest

[Leavrth]

/retest

[hawkingrei]

/retest

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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