-
Notifications
You must be signed in to change notification settings - Fork 282
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
test(ticdc): fix bank failure caused by wrong snapshot in db session (#8212) #8276
base: release-6.1
Are you sure you want to change the base?
test(ticdc): fix bank failure caused by wrong snapshot in db session (#8212) #8276
Conversation
[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 The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
@ti-chi-bot: This cherry pick PR is for a release branch and has not yet been approved by release team. 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. 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. |
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## release-6.1 #8276 +/- ##
================================================
Coverage ? 60.8653%
================================================
Files ? 895
Lines ? 123535
Branches ? 0
================================================
Hits ? 75190
Misses ? 41990
Partials ? 6355 |
This is an automated cherry-pick of #8212
What problem does this PR solve?
Issue Number: close #8211
What is changed and how it works?
*sql.DB
holds a connection pool, it returns a random idle connection, in the bank test we need to ensure the database connection has the same snapshot during verification.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