Skip to content

[DNM just run ci for hotfix#5040

Closed
lidezhu wants to merge 1 commit intopingcap:release-5.4-20220531from
lidezhu:hotfix-5.4-0531-02
Closed

[DNM just run ci for hotfix#5040
lidezhu wants to merge 1 commit intopingcap:release-5.4-20220531from
lidezhu:hotfix-5.4-0531-02

Conversation

@lidezhu
Copy link
Contributor

@lidezhu lidezhu commented May 31, 2022

What problem does this PR solve?

Issue Number: close #xxx

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

None

@ti-chi-bot
Copy link
Member

ti-chi-bot commented May 31, 2022

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Details

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

@ti-chi-bot ti-chi-bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/cherry-pick-not-approved labels May 31, 2022
@ti-chi-bot
Copy link
Member

ti-chi-bot commented May 31, 2022

@lidezhu: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

Details

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.

@ti-chi-bot ti-chi-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label May 31, 2022
@lidezhu
ignore delmark when add minmax for pk column (pingcap#4746) (pingcap#…
03b2bd4 
…4963)

* ignore delmark when add minmax for pk column (pingcap#4746)

close pingcap#4747

* fix static analysis

* use release-5.4 branch image for other components

* fix fullstack image
@lidezhu lidezhu force-pushed the hotfix-5.4-0531-02 branch from 0dbaffe to 03b2bd4 Compare May 31, 2022 10:40
@ti-chi-bot ti-chi-bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels May 31, 2022
@lidezhu lidezhu changed the title ignore delmark when add minmax for pk column (#4746) [WIP] ignore delmark when add minmax for pk column (#4746) May 31, 2022
@ti-chi-bot ti-chi-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 31, 2022
@lidezhu lidezhu changed the title [WIP] ignore delmark when add minmax for pk column (#4746) [DNM ignore delmark when add minmax for pk column (#4746) May 31, 2022
@ti-chi-bot ti-chi-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 31, 2022
@lidezhu lidezhu changed the title [DNM ignore delmark when add minmax for pk column (#4746) [DNM just run ci for hotfix May 31, 2022
@lidezhu
Copy link
Contributor Author

lidezhu commented May 31, 2022

/run-all-tests

@sre-bot
Copy link
Collaborator

sre-bot commented May 31, 2022

lines: 43.5% (50233 out of 115432)
branches: 6.5% (82253 out of 1266067)

@lidezhu lidezhu closed this May 31, 2022
@lidezhu lidezhu reopened this May 31, 2022
@lidezhu lidezhu closed this May 31, 2022
@lidezhu lidezhu mentioned this pull request May 31, 2022
Merged
12 tasks
@sre-bot
Copy link
Collaborator

sre-bot commented May 31, 2022

lines: 43.5% (50227 out of 115432)
branches: 6.5% (82248 out of 1266067)

@lidezhu lidezhu reopened this Jun 14, 2022
@lidezhu lidezhu closed this Jun 14, 2022
@sre-bot
Copy link
Collaborator

sre-bot commented Jun 14, 2022

lines: 43.5% (50230 out of 115432)
branches: 6.5% (82256 out of 1266067)

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

Reviewers

No reviews

Assignees

No one assigned

Labels

do-not-merge/cherry-pick-not-approved release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@lidezhu @ti-chi-bot @sre-bot