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.

Sign up for GitHub

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

Jump to bottom

Fix the fail start of tiflash because of the zero division when getting cpu number (#9602) #9627

Open
wants to merge 5 commits into
base: release-6.5
Choose a base branch
from
Open

Fix the fail start of tiflash because of the zero division when getting cpu number (#9602) #9627

wants to merge 5 commits into from

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #9602

What problem does this PR solve?

Issue Number: close #9212

Problem Summary:

What is changed and how it works?

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No code

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

Fix the that fail to start tiflash because of the zero division when getting cpu number

@xzhangxian1008 @ti-chi-bot
This is an automated cherry-pick of pingcap#9602
6c1a5a1 
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot ti-chi-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-6.5 This PR is cherry-picked to release-6.5 from a source PR. labels Nov 15, 2024
@ti-chi-bot ti-chi-bot mentioned this pull request Nov 15, 2024
Merged
12 tasks
@ti-chi-bot ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Nov 15, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign ichn-hu for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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 cherry-pick-approved Cherry pick PR approved by release team. and removed do-not-merge/cherry-pick-not-approved labels Nov 15, 2024
@xzhangxian1008
Copy link
Contributor

/run-all-tests

1 similar comment
@xzhangxian1008
Copy link
Contributor

/run-all-tests

@xzhangxian1008
Copy link
Contributor

/retest

3 similar comments
@xzhangxian1008
Copy link
Contributor

/retest

@xzhangxian1008
Copy link
Contributor

/retest

@xzhangxian1008
Copy link
Contributor

/retest

@xzhangxian1008
Copy link
Contributor

/hold

@ti-chi-bot ti-chi-bot bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 26, 2024
@purelind
Copy link
Collaborator

purelind commented Dec 1, 2024

/retest

@purelind
Copy link
Collaborator

purelind commented Dec 1, 2024

/test pull-integration-test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@xzhangxian1008 xzhangxian1008

Labels
cherry-pick-approved Cherry pick PR approved by release team. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. type/cherry-pick-for-release-6.5 This PR is cherry-picked to release-6.5 from a source PR.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@ti-chi-bot @xzhangxian1008 @purelind @JaySon-Huang