lhotari opened a new pull request, #17743:
URL: https://github.com/apache/pulsar/pull/17743

   Fixes #17714
   
   ### Motivation
   
   There are a few resource leaks in tests where setup (or internalSetup) is 
called explicitly without first calling cleanup.
   This causes a thread and memory leak in tests which slows down test 
execution.
   
   ### Modifications
   
   - when setup is called explicitly, cleanup should be issued before it
   - remove unnecessary "resetConfig" method calls
     - resetConfig gets called as part of internalCleanup
     - when resetConfig is in cleanup, it's possible to override config before 
calling setup
       - this allows using setup & cleanup methods instead of using error prone 
internalSetup and internalCleanup methods which might leave something behind
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [ ] `doc-required` 
   (Your PR needs to update docs and you will update later)
   
   - [x] `doc-not-needed` 
   (Please explain why)
   
   - [ ] `doc` 
   (Your PR contains doc changes)
   
   - [ ] `doc-complete`
   (Docs have been already added)
   
   ### Matching PR in forked repository
   
   PR in forked repository: <!-- ENTER URL HERE 
   
   After opening this PR, the build in apache/pulsar will fail and instructions 
will
   be provided for opening a PR in the PR author's forked repository.
   
   apache/pulsar pull requests should be first tested in your own fork since 
the 
   apache/pulsar CI based on GitHub Actions has constrained resources and quota.
   GitHub Actions provides separate quota for pull requests that are executed 
in 
   a forked repository.
   
   The tests will be run in the forked repository until all PR review comments 
have
   been handled, the tests pass and the PR is approved by a reviewer.
   
   -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to