Skip to content
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) #50170

Merged

Conversation

ti-chi-bot
Copy link
Member

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

  • 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

@ti-chi-bot ti-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-7.5 This PR is cherry-picked to release-7.5 from a source PR. labels Jan 8, 2024
@ti-chi-bot ti-chi-bot mentioned this pull request Jan 8, 2024
12 tasks
Copy link

codecov bot commented Jan 8, 2024

Codecov Report

❗ No coverage uploaded for pull request base (release-7.5@de2293d). Click here to learn what that means.
The diff coverage is 68.7500%.

Additional details and impacted files
@@               Coverage Diff                @@
##             release-7.5     #50170   +/-   ##
================================================
  Coverage               ?   73.6251%           
================================================
  Files                  ?       1404           
  Lines                  ?     421921           
  Branches               ?          0           
================================================
  Hits                   ?     310640           
  Misses                 ?      91866           
  Partials               ?      19415           
Flag Coverage Δ
unit 73.6251% <68.7500%> (?)

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

Components Coverage Δ
dumpling 53.9913% <0.0000%> (?)
parser ∅ <0.0000%> (?)
br 53.8069% <0.0000%> (?)

@ti-chi-bot ti-chi-bot added the cherry-pick-approved Cherry pick PR approved by release team. label Feb 2, 2024
@ekexium ekexium closed this Feb 20, 2024
@ekexium ekexium reopened this Feb 20, 2024
@ekexium ekexium requested review from cfzjywxk and zyguan February 20, 2024 03:15
@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Feb 20, 2024
Copy link

ti-chi-bot bot commented Feb 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: you06, 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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Feb 20, 2024
Copy link

ti-chi-bot bot commented Feb 20, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-02-20 03:22:05.228308447 +0000 UTC m=+327413.975931557: ☑️ agreed by you06.
  • 2024-02-20 03:23:28.106992643 +0000 UTC m=+327496.854615749: ☑️ agreed by zyguan.

@ti-chi-bot ti-chi-bot bot merged commit 245dd62 into pingcap:release-7.5 Feb 20, 2024
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved cherry-pick-approved Cherry pick PR approved by release team. lgtm release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-7.5 This PR is cherry-picked to release-7.5 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants