fix: check kill signal against 0

[ekexium]

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

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test
  • Simple enough change.

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 @ekexium. 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/test-infra repository.

[codecov]

Codecov Report

Merging #50029 (a17c279) into master (b50b151) will decrease coverage by 3.1667%.
Report is 51 commits behind head on master.
The diff coverage is 28.1250%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #50029        +/-   ##
================================================
- Coverage   71.9505%   68.7838%   -3.1668%     
================================================
  Files          1438       1440         +2     
  Lines        345800     407350     +61550     
================================================
+ Hits         248805     280191     +31386     
- Misses        76750     108164     +31414     
+ Partials      20245      18995      -1250     

Flag	Coverage Δ
integration	44.0947% <28.1250%> (?)
unit	71.9166% <ø> (-0.0340%)	⬇️

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

Components	Coverage Δ
dumpling	56.3129% <ø> (ø)
parser	∅ <ø> (∅)
br	44.1250% <ø> (-7.4996%)	⬇️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

• OWNERS [jackysp,zyguan]

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-01-05 08:46:50.306383612 +0000 UTC m=+999.890637298: ☑️ agreed by zyguan.
• 2024-01-08 03:20:06.367597195 +0000 UTC m=+240595.951850882: ☑️ agreed by jackysp.

[tiprow]

@ekexium: 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
tiprow_fast_test	a17c279	link	true	/test tiprow_fast_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/test-infra repository. I understand the commands that are listed here.

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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