-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
br: avoid wrong warning (#56492) #57888
br: avoid wrong warning (#56492) #57888
Conversation
Signed-off-by: Jianjun Liao <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BornChanger, Leavrth 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:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
/retest |
1 similar comment
/retest |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-7.5 #57888 +/- ##
================================================
Coverage ? 72.1670%
================================================
Files ? 1415
Lines ? 413000
Branches ? 0
================================================
Hits ? 298050
Misses ? 94972
Partials ? 19978
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This is an automated cherry-pick of #56492
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
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.