Skip to content

ttl: make ttl manually trigger stable (#45869)#45897

Closed
ti-chi-bot wants to merge 1 commit intopingcap:release-7.3from
ti-chi-bot:cherry-pick-45869-to-release-7.3
Closed

ttl: make ttl manually trigger stable (#45869)#45897
ti-chi-bot wants to merge 1 commit intopingcap:release-7.3from
ti-chi-bot:cherry-pick-45869-to-release-7.3

Conversation

@ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #45869

What problem does this PR solve?

Issue Number: close #45868

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

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/S Denotes a PR that changes 10-29 lines, ignoring generated files. type/cherry-pick-for-release-7.3 labels Aug 8, 2023
@ti-chi-bot
Copy link

ti-chi-bot bot commented Aug 8, 2023

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
Copy link

ti-chi-bot bot commented Aug 8, 2023

[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 gmhdbjd for approval. For more information see the Kubernetes Code Review Process.

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

Details 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

@codecov
Copy link

codecov bot commented Aug 8, 2023

Codecov Report

❗ No coverage uploaded for pull request base (release-7.3@203d839). Click here to learn what that means.
The diff coverage is n/a.

Additional details and impacted files
@@               Coverage Diff                @@
##             release-7.3     #45897   +/-   ##
================================================
  Coverage               ?   73.1974%           
================================================
  Files                  ?       1266           
  Lines                  ?     390735           
  Branches               ?          0           
================================================
  Hits                   ?     286008           
  Misses                 ?      86371           
  Partials               ?      18356           
Flag Coverage Δ
unit 73.1974% <0.0000%> (?)

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

Components Coverage Δ
dumpling 54.0444% <0.0000%> (?)
parser 85.0359% <0.0000%> (?)
br 52.0257% <0.0000%> (?)

@lcwangchao lcwangchao closed this Aug 8, 2023
@ti-chi-bot ti-chi-bot deleted the cherry-pick-45869-to-release-7.3 branch April 15, 2025 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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. type/cherry-pick-for-release-7.3

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants