br: fix unstable test br_file_corruption

[3pointer]

What problem does this PR solve?

Issue Number: ref #53835
Problem Summary:
previous implement about the test has a bug, when the broken sst file is not belong to user table(systable), and it will not restore by default. so the restore could success but expect to fail.

What changed and how does it work?

fix the case by change every sst 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

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tiprow]

Hi @3pointer. 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.

[3pointer]

/run-br-integration-tests

[3pointer]

/test pull-br-integration-test

[ti-chi-bot]

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

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test unit-test

The following commands are available to trigger optional jobs:

/test pull-br-integration-test

/test pull-common-test

/test pull-e2e-test

/test pull-integration-binlog-test

/test pull-integration-common-test

/test pull-integration-copr-test

/test pull-integration-ddl-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-tidb-tools-test

/test pull-sqllogic-test

/test pull-tiflash-test

Use /test all to run the following jobs that were automatically triggered:

pingcap/tidb/release-7.1/ghpr_build

pingcap/tidb/release-7.1/ghpr_check

pingcap/tidb/release-7.1/ghpr_check2

pingcap/tidb/release-7.1/ghpr_mysql_test

pingcap/tidb/release-7.1/ghpr_unit_test

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.

[3pointer]

/test pull-br-integration-test

[ti-chi-bot]

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

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test unit-test

The following commands are available to trigger optional jobs:

/test pull-br-integration-test

/test pull-common-test

/test pull-e2e-test

/test pull-integration-binlog-test

/test pull-integration-common-test

/test pull-integration-copr-test

/test pull-integration-ddl-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-tidb-tools-test

/test pull-sqllogic-test

/test pull-tiflash-test

Use /test all to run the following jobs that were automatically triggered:

pingcap/tidb/release-7.1/ghpr_build

pingcap/tidb/release-7.1/ghpr_check

pingcap/tidb/release-7.1/ghpr_check2

pingcap/tidb/release-7.1/ghpr_mysql_test

pingcap/tidb/release-7.1/ghpr_unit_test

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.

[tiprow]

@3pointer: 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.

[tiprow]

@ti-chi-bot[bot]: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

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

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test unit-test

The following commands are available to trigger optional jobs:

/test pull-br-integration-test

/test pull-common-test

/test pull-e2e-test

/test pull-integration-binlog-test

/test pull-integration-common-test

/test pull-integration-copr-test

/test pull-integration-ddl-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-tidb-tools-test

/test pull-sqllogic-test

/test pull-tiflash-test

Use /test all to run the following jobs that were automatically triggered:

pingcap/tidb/release-7.1/ghpr_build

pingcap/tidb/release-7.1/ghpr_check

pingcap/tidb/release-7.1/ghpr_check2

pingcap/tidb/release-7.1/ghpr_mysql_test

pingcap/tidb/release-7.1/ghpr_unit_test

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.

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.

[3pointer]

/ok-to-test

[tiprow]

@3pointer: No presubmit jobs available for pingcap/tidb@release-7.1

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.

[tiprow]

@ti-chi-bot[bot]: No presubmit jobs available for pingcap/tidb@release-7.1

In response to this:

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

/test build

/test check-dev

/test check-dev2

/test mysql-test

/test unit-test

The following commands are available to trigger optional jobs:

/test pull-br-integration-test

/test pull-common-test

/test pull-e2e-test

/test pull-integration-binlog-test

/test pull-integration-common-test

/test pull-integration-copr-test

/test pull-integration-ddl-test

/test pull-integration-jdbc-test

/test pull-integration-mysql-test

/test pull-integration-tidb-tools-test

/test pull-sqllogic-test

/test pull-tiflash-test

Use /test all to run the following jobs that were automatically triggered:

pingcap/tidb/release-7.1/ghpr_build

pingcap/tidb/release-7.1/ghpr_check

pingcap/tidb/release-7.1/ghpr_check2

pingcap/tidb/release-7.1/ghpr_mysql_test

pingcap/tidb/release-7.1/ghpr_unit_test

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.

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.

[3pointer]

/test pull-br-integration-test

[tiprow]

@3pointer: No presubmit jobs available for pingcap/tidb@release-7.1

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (release-7.1@5228e2f). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.1     #59965   +/-   ##
================================================
  Coverage               ?   73.4787%           
================================================
  Files                  ?       1213           
  Lines                  ?     382154           
  Branches               ?          0           
================================================
  Hits                   ?     280802           
  Misses                 ?      83420           
  Partials               ?      17932           

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ti-chi-bot]

@3pointer: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-br-integration-test	7ab5262	link	false	/test pull-br-integration-test

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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:

• OWNERS [lance6716]

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:

• 2025-03-08 15:24:20.343546054 +0000 UTC m=+23815.949074981: ☑️ agreed by lance6716.