-
Notifications
You must be signed in to change notification settings - Fork 288
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
sink(ticdc): add some integration tests for storage sink (#9124) #9171
Merged
ti-chi-bot
merged 1 commit into
pingcap:release-7.1
from
ti-chi-bot:cherry-pick-9124-to-release-7.1
Jul 3, 2023
Merged
sink(ticdc): add some integration tests for storage sink (#9124) #9171
ti-chi-bot
merged 1 commit into
pingcap:release-7.1
from
ti-chi-bot:cherry-pick-9124-to-release-7.1
Jul 3, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ti-chi-bot
added
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
type/cherry-pick-for-release-7.1
This PR is cherry-picked to release-7.1 from a source PR.
labels
Jun 9, 2023
ti-chi-bot
bot
added
do-not-merge/cherry-pick-not-approved
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
labels
Jun 9, 2023
ti-chi-bot
added
the
cherry-pick-approved
Cherry pick PR approved by release team.
label
Jun 9, 2023
CharlesCheung96
force-pushed
the
cherry-pick-9124-to-release-7.1
branch
from
June 30, 2023 10:26
f666320
to
7d6e19e
Compare
/test all |
asddongmen
approved these changes
Jun 30, 2023
ti-chi-bot
bot
added
needs-1-more-lgtm
Indicates a PR needs 1 more LGTM.
approved
labels
Jun 30, 2023
3AceShowHand
approved these changes
Jul 3, 2023
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 3AceShowHand, asddongmen 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 |
[LGTM Timeline notifier]Timeline:
|
CharlesCheung96
force-pushed
the
cherry-pick-9124-to-release-7.1
branch
from
July 3, 2023 02:44
7d6e19e
to
5b876a0
Compare
/test all |
CharlesCheung96
force-pushed
the
cherry-pick-9124-to-release-7.1
branch
from
July 3, 2023 03:07
5b876a0
to
c02a6de
Compare
/test all |
CharlesCheung96
force-pushed
the
cherry-pick-9124-to-release-7.1
branch
from
July 3, 2023 04:13
c02a6de
to
ddf4683
Compare
/test all |
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
Denotes a PR that will be considered when it comes time to generate release notes.
size/XXL
Denotes a PR that changes 1000+ lines, ignoring generated files.
type/cherry-pick-for-release-7.1
This PR is cherry-picked to release-7.1 from a source PR.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated cherry-pick of #9124
What problem does this PR solve?
Issue Number: ref #8772
What is changed and how it works?
improving tests of storage sink
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note