Skip to content
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

Resolve a LEAK warning in unit test #642

Merged
merged 1 commit into from Apr 8, 2024

Conversation

cty123
Copy link
Contributor

@cty123 cty123 commented Mar 16, 2024

Make sure that:

  • [ x ] You have read the contribution guidelines.
  • [ x ] You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
  • [ x ] You use the code formatters provided here and have them applied to your changes. Don't submit any formatting related changes.
  • [ x ] You submit test cases (unit or integration tests) that back your changes.

Issue description

Previously the expected message wasn't released after the unit test, and this causes test runs to printout the LEAK warning as reported in the issue #580. It's not a real issue, but would be nice to fix.

New Public APIs

Additional context

@mp911de mp911de added the type: task A general task label Apr 8, 2024
@mp911de mp911de added this to the 1.0.5.RELEASE milestone Apr 8, 2024
@mp911de mp911de merged commit 2d9a921 into pgjdbc:main Apr 8, 2024
1 check passed
@mp911de mp911de self-assigned this Apr 8, 2024
mp911de pushed a commit that referenced this pull request Apr 8, 2024
@mp911de
Copy link
Collaborator

mp911de commented Apr 8, 2024

Thank you for your contribution. That's merged and backported now.

@mp911de mp911de changed the title test: resolve a LEAK warning in unit test Resolve a LEAK warning in unit test Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants