divijvaidya commented on PR #13956: URL: https://github.com/apache/kafka/pull/13956#issuecomment-1632593879
>Did you verify the thread leak by checking the threat dump? No, I found the leak from a very useful line in the tests I added recently. It prints the names of the leaked thread, `Found 3 unexpected threads during @AfterAll: `controller-event-thread,daemon-bounce-broker-EventThread,Test worker-EventThread` ==> expected: <true> but was: <false>` @philipnee I wanted your expert opinion on the possible reason for failure of `ConsumerBounceTest > testConsumptionWithBrokerFailures`. See the stack trace in the description. Is there anything that pops in your head that could make it less flaky (given where it fails in the stacktrace). Asking because, this failure was the cause of mayhem which leaked threads. -- 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: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
