Closed zimulala closed 1 month ago
Hi @zimulala. 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.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 74.9529%. Comparing base (
6aef624
) to head (8b1dce0
). Report is 7 commits behind head on master.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Defined2014, tangenta
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Timeline:
2024-05-15 04:26:21.364238863 +0000 UTC m=+1627335.121374435
: :ballot_box_with_check: agreed by Defined2014.2024-05-15 06:08:18.337950202 +0000 UTC m=+1633452.095085776
: :ballot_box_with_check: agreed by tangenta./retest-required
@zimulala: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
/run-cherry-picker
In response to a cherrypick label: new pull request created to branch release-7.5
: #53408.
In response to a cherrypick label: new pull request created to branch release-8.1
: #53409.
What problem does this PR solve?
Issue Number: close https://github.com/pingcap/tidb/issues/53281
Problem Summary: Both scenarios are explained in the issue.
Introduce code for this issue: https://github.com/pingcap/tidb/pull/50624/files#diff-45ad039a8b87835b475a52615355c444538d3a1f31a84d7b3ac94e15b1ce8721R126-R127
What changed and how does it work?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.