You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by GitBox <gi...@apache.org> on 2021/02/03 13:45:24 UTC

[GitHub] [kafka] chia7712 commented on pull request #9972: KAFKA-8779: Reintroduce flaky tests

chia7712 commented on pull request #9972:
URL: https://github.com/apache/kafka/pull/9972#issuecomment-772516599


   > The cause of the flakiness appears to have been lack of test isolation between those tests and other tests which manipulate log levels (which are effectively global to the JVM). In general there are quite a few tests which manipulate log4j and/or make assertions on log4j global state, so introduce some of helpers to try to get test isolation across the whole of the broker code.
   
   IIRC, gradle forks `n` JVMs to run `n` tests parallel and tests in same JVM are executed sequentially. Hence, could we reset log4j state (maybe in `@AfterEach`) instead of global locking? Please correct me if I misunderstand the root cause. 


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