-
Notifications
You must be signed in to change notification settings - Fork 49
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
Fix the out parameter test failuer in Postgres DB #760
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #760 +/- ##
============================================
- Coverage 80.11% 79.82% -0.30%
Complexity 109 109
============================================
Files 41 41
Lines 3933 3926 -7
Branches 666 666
============================================
- Hits 3151 3134 -17
- Misses 526 537 +11
+ Partials 256 255 -1 ☔ View full report in Codecov by Sentry. |
Quality Gate passedIssues Measures |
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.
LGTM
Purpose
Fixes: ballerina-platform/ballerina-library#7445
Fixes: ballerina-platform/ballerina-library#7380
The fix introduced for the issue ballerina-platform/ballerina-library#7255 only addresses default result processors. When there is a custom processor, it still fails. This PR is to fix it.
With the fix, unit tests written in OutParameterProcessorTest.java is not valid, Hence removing them.
Examples
Checklist