Hi Gary, On Wed, 11 Sept 2024 at 22:13, Gary D. Gregory <ggreg...@apache.org> wrote: > Running 'mvn clean install' on git main [1] gives me: > > [ERROR] Failures: > [ERROR] AsyncLoggerConfigTest.testSingleFilterInvocation:114 > Wanted but not invoked: > appender.append(<any>); > -> at > org.apache.logging.log4j.async.logger.AsyncLoggerConfigTest.testSingleFilterInvocation(AsyncLoggerConfigTest.java:114) > > However, there was exactly 1 interaction with this mock: > appender.getName(); > -> at > org.apache.logging.log4j.core.config.AppenderControl.<init>(AppenderControl.java:50)
In this test a message is sent through `AsyncLoggerConfig` and we wait up to 100 ms until `Appender.append()` is called on the asynchronous thread. I guess this _might_ fail on an extremely busy host. If your host was not so busy, we might have a performance problem with LMAX Disruptor. I bumped the maximum delay to up to 1 s, hope it helps. Piotr PS: On a side note: `log4j-mongodb` might fail on some hosts (e.g. my Debian 12), since it requires some specific versions of OpenSSL and other libraries. That is why I proposed to start the Mongo server from Docker in [1]. [1] https://github.com/apache/logging-log4j2/pull/2922
