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

   ### Motivation
   
   Fixing Netty ByteBuf leaks in test code is needed for executing the plan 
explained in [Enhancing Pulsar CI with Netty leak detection and 
reporting](https://lists.apache.org/thread/fh63hg31womzr64bc7djv3sovgcx6z99). 
The Pulsar CI Netty leak detection and reporting solution was added in #24272.
   
   ### Modifications
   
   - Fix thread leaks in these tests:
     - ProxySaslAuthenticationTest (indent was also changed from tabs to spaces)
     - BookieRackAffinityMappingTest
     - RateLimiterTest 
     - FileSystemOffloaderLocalFileTest
     - Fix thread leaks in tests using BookKeeperClusterTestCase base class
   - Fix ByteBuf leaks in these tests
     - FileSystemManagedLedgerOffloaderTest
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [ ] `doc` <!-- Your PR contains doc changes. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update 
later -->
   - [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `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