Hong-Yi Chen dc82c766fa KAFKA-18834 Fix LoggingResourceTest#testSetLevelDefaultScope (#19920) ... - Flaky behavior `LoggingResourceTest#testSetLevelDefaultScope` sometimes fails by not capturing its expected WARN log. - Root cause Both `LoggersTest#testSetLevelWithValidRootLoggerNames` and `LoggingResourceTest#testSetLevelDefaultScope` may share the same `LoggerContext` when executed in the same JVM. `LoggersTest#testSetLevelWithValidRootLoggerNames` calls `loggers.setLevel("", ERROR)`, which mutates the global root logger level to ERROR and suppresses WARN logs, which causes subsequent tests to fail to emit WARN-level output. - Fix in this PR Resets the Log4j configuration after each test in `LoggersTest`, ensuring that any global changes are reverted. Reviewers: Chia-Ping Tsai <chia7712@gmail.com>		2025-06-26 13:39:08 +08:00
..
main	KAFKA-19140 ConnectAssignor#performAssignment parameter can be replace to ConnectProtocolCompatibility (#19476)	2025-06-20 03:07:57 +08:00
test	KAFKA-18834 Fix LoggingResourceTest#testSetLevelDefaultScope (#19920)	2025-06-26 13:39:08 +08:00