-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
fix: check kill signal against 0 (#50029) #50168
fix: check kill signal against 0 (#50029) #50168
Conversation
Signed-off-by: ti-chi-bot <[email protected]>
Signed-off-by: ekexium <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cfzjywxk, zyguan 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 |
/retest |
…k-50029-to-release-7.1
/retest |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-7.1 #50168 +/- ##
================================================
Coverage ? 73.3649%
================================================
Files ? 1211
Lines ? 380408
Branches ? 0
================================================
Hits ? 279086
Misses ? 83519
Partials ? 17803 |
This is an automated cherry-pick of #50029
What problem does this PR solve?
Issue Number: ref #49643
Problem Summary:
Previously the kill signal was checked against
1
, however TiDB uses non-zero values to indicate a kill signal.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.