Closed 3pointer closed 1 week ago
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
/ok-to-test
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.
/test pull-br-integration-test
@3pointer: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test fast_test_tiprow
/test tidb_parser_test
Use /test all
to run all jobs.
Attention: Patch coverage is 81.20000%
with 47 lines
in your changes missing coverage. Please review.
Project coverage is 56.6870%. Comparing base (
b23ac8e
) to head (7230ed8
). Report is 14 commits behind head on master.
@Leavrth: Your lgtm message is repeated, so it is ignored.
/test unit-test
@3pointer: The specified target(s) for /test
were not found.
The following commands are available to trigger required jobs:
/test fast_test_tiprow
/test tidb_parser_test
Use /test all
to run all jobs.
[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
What problem does this PR solve?
Issue Number: close https://github.com/pingcap/tidb/issues/52534 close https://github.com/pingcap/tidb/issues/53519 Problem Summary:
What changed and how does it work?
storewatch
to observe store change event to retry backup.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.