[GitHub] [pulsar] lhotari edited a comment on pull request #9626: [Testing] Add debugging feature which leaves integration test containers running after test completes

[GitBox <gi...@apache.org>]

lhotari edited a comment on pull request #9626:
URL: https://github.com/apache/pulsar/pull/9626#issuecomment-782144592


   @bsideup Thanks for your comments. In this case, the changes in this PR aren't meant to be used in CI at all. The reason to leave the container running is to debug an issue locally. I've had the impression that it's the reason why `TESTCONTAINERS_RYUK_DISABLED=true` exists. At least, that's how I've been using it in the past. 
   
   Would you also recommend using the reusable container mode for also for the debugging use case that I have described? I guess that would require also enabling `testcontainers.reuse.enable` in `~/.testcontainers.properties`?  
   
   I have one concern. The problem with reusable container mode is that it impacts the execution when a container gets reused. I'd simply like to leave the containers after the test and the test JVM completes so that I could open a shell to the container and inspect the state. Perhaps this would be a feature request for Testcontainers? 
   Is there a workaround with reusable containers by adding a random label to the container etc so that the container would never get reused?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org