I just pulled main since we've had changes there, now I get: [ERROR] Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 15.31 s <<< FAILURE! -- in org.apache.logging.log4j.core.appender.SocketAppenderReconnectTest [ERROR] org.apache.logging.log4j.core.appender.SocketAppenderReconnectTest.repeating_reconnect_failures_should_be_propagated -- Time elapsed: 3.323 s <<< ERROR! org.apache.logging.log4j.core.appender.AppenderLoggingException: Error writing to TCP:localhost:57111 for connection localhost/127.0.0.1:57111 at org.apache.logging.log4j.core.net.TcpSocketManager.write(TcpSocketManager.java:211) at org.apache.logging.log4j.core.appender.OutputStreamManager.write(OutputStreamManager.java:181) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.writeByteArrayToManager(AbstractOutputStreamAppender.java:218) at org.apache.logging.log4j.core.appender.SocketAppender.directEncodeEvent(SocketAppender.java:338) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.tryAppend(AbstractOutputStreamAppender.java:202) at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:193) at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:155) at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:128) at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:119) at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:83) at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:626) at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:586) at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:562) at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:496) at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:92) at org.apache.logging.log4j.core.Logger.doLog(Logger.java:158) at org.apache.logging.log4j.kit.logger.AbstractLogger.tryLogMessage(AbstractLogger.java:266) at org.apache.logging.log4j.kit.logger.AbstractLogger.logMessageTrackRecursion(AbstractLogger.java:234) at org.apache.logging.log4j.kit.logger.AbstractLogger.logMessageSafely(AbstractLogger.java:215) at org.apache.logging.log4j.kit.logger.AbstractLogger.logMessage(AbstractLogger.java:340) at org.apache.logging.log4j.kit.logger.AbstractLogger.logIfEnabled(AbstractLogger.java:1092) at org.apache.logging.log4j.kit.logger.AbstractLogger.info(AbstractLogger.java:2336) at org.apache.logging.log4j.core.appender.SocketAppenderReconnectTest.lambda$verifyLoggingSuccess$2(SocketAppenderReconnectTest.java:361) at org.awaitility.core.CallableCondition$ConditionEvaluationWrapper.eval(CallableCondition.java:99) at org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:248) at org.awaitility.core.ConditionAwaiter$ConditionPoller.call(ConditionAwaiter.java:235) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:840) Caused by: java.net.SocketException: Connection reset by peer at java.base/sun.nio.ch.NioSocketImpl.implWrite(NioSocketImpl.java:425) at java.base/sun.nio.ch.NioSocketImpl.write(NioSocketImpl.java:445) at java.base/sun.nio.ch.NioSocketImpl$2.write(NioSocketImpl.java:831) at java.base/java.net.Socket$SocketOutputStream.write(Socket.java:1035) at org.apache.logging.log4j.core.net.TcpSocketManager.writeAndFlush(TcpSocketManager.java:221) at org.apache.logging.log4j.core.net.TcpSocketManager.write(TcpSocketManager.java:182) ... 29 more
Gary On 2024/09/12 12:08:07 "Gary D. Gregory" wrote: > On 2024/09/12 06:51:22 "Piotr P. Karwasz" wrote: > > 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. > > Thank you Piotr. > > When I run a build, I run it and then do other work on my PC, so I expect the > CPU usage to go and down a lot. It would be nice if we could find a way to > use structures like count down latches to sync up some tests. The build is > running now... ;-) > > Gary > > > > > 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 > > >