clolov commented on PR #13260: URL: https://github.com/apache/kafka/pull/13260#issuecomment-1658242751
It appears that in Zookeeper 3.8.0 the Zookeeper community moved away from log4j to logback (source: https://issues.apache.org/jira/browse/ZOOKEEPER-4427) In the failing test cases we attach an appender to the root logger (Kafka uses a log4j logger) and assert that we see certain log messages. Because of the mismatch in expectation (log4j) and reality (logback) these tests have started failing as the test-appender has no messages. The difference in Zookeeper dependencies between current trunk (31 July 2023) and this pull request is: ``` trunk org.apache.zookeeper:zookeeper:3.6.4 > io.netty:netty-handler:4.1.94.Final > io.netty:netty-transport-native-epoll:4.1.94.Final > org.apache.yetus:audience-annotations:0.13.0 > org.apache.zookeeper:zookeeper-jute:3.6.4 > org.slf4j:slf4j-api:1.7.36 pull request org.apache.zookeeper:zookeeper:3.8.2 > ch.qos.logback:logback-classic:1.2.10 <- NEW > ch.qos.logback:logback-core:1.2.10 <- NEW > commons-io:commons-io:2.11.0 <- NEW > io.netty:netty-handler:4.1.94.Final > io.netty:netty-transport-native-epoll:4.1.94.Final > org.apache.yetus:audience-annotations:0.12.0 > org.apache.zookeeper:zookeeper-jute:3.8.2 > org.slf4j:slf4j-api:1.7.36 ``` I have removed the `ch.qos.logback:*` dependencies in the latest commit and tests have started passing locally. -- 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