br: fix br integration test file corruption

[Leavrth]

What problem does this PR solve?

Issue Number: close #53835

Problem Summary:
The log file may not be restored so sometimes corrupting one log file does not make restore fail.

What changed and how does it work?

lost/corrupt all the files.

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.4799%. Comparing base (ba5823b) to head (b318a65).
Report is 60 commits behind head on master.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #56799         +/-   ##
=================================================
- Coverage   73.3727%   57.4799%   -15.8929%     
=================================================
  Files          1635       1761        +126     
  Lines        452770     638477     +185707     
=================================================
+ Hits         332210     366996      +34786     
- Misses       100208     247135     +146927     
- Partials      20352      24346       +3994     

Flag	Coverage Δ
integration	38.8810% <ø> (?)
unit	73.1888% <ø> (+0.6962%)	⬆️

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

Components	Coverage Δ
dumpling	52.9478% <ø> (ø)
parser	∅ <ø> (∅)
br	63.0958% <ø> (+17.0727%)	⬆️

[Leavrth]

/test pull-br-integration-test

[tiprow]

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

In response to this:

/test pull-br-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-sigs/prow repository.

[Tristan1900]

/lgtm

[ti-chi-bot]

@Tristan1900: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

/lgtm

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.

[Leavrth]

/ok-to-test

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 3pointer, Tristan1900, 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-28 02:33:20.516228028 +0000 UTC m=+230713.355383574: ☑️ agreed by YuJuncen.
• 2024-10-28 02:43:13.569592845 +0000 UTC m=+231306.408748388: ☑️ agreed by 3pointer.

[Leavrth]

/retest

[ti-chi-bot]

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