- Notifications
You must be signed in to change notification settings - Fork311
Improve DTC test stability#3181
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Looks pretty good to me.
codecovbot commentedFeb 26, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@## main #3181 +/- ##==========================================- Coverage 72.96% 72.80% -0.16%========================================== Files 283 285 +2 Lines 58997 59137 +140 ==========================================+ Hits 43048 43057 +9- Misses 15949 16080 +131
Flags with carried forward coverage won't be shown.Click here to find out more. ☔ View full report in Codecov by Sentry. |
e65635b
intomainUh oh!
There was an error while loading.Please reload this page.
I had originally thought that the outcome of TransactionAbortedException vs TransactionInDoubtException was dependent on sql server type (azure vs. local). However, I now understand that this is timing based and the azure database test invocations can also result in TransactionInDoubtException. Update the test to check for either of the expected error conditions.