[ https://issues.apache.org/jira/browse/LOG4NET-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203723#comment-17203723 ]
Davyd McColl commented on LOG4NET-649: -------------------------------------- This test passes on Windows and Linux: [https://github.com/fluffynuts/log4net-consumers/blob/master/netcore3.1-consumer/TestMemoryAppender.cs|https://github.com/fluffynuts/log4net-consumers/blob/master/netcore3.1-consumer/TestMemoryAppender.cs], which leads me to believe that something is different between our environments. The setup there is quite simple -- perhaps you can help find out what's different? > MemoryAppender doesn't work on Alpine Linux with 2.0.10 > ------------------------------------------------------- > > Key: LOG4NET-649 > URL: https://issues.apache.org/jira/browse/LOG4NET-649 > Project: Log4net > Issue Type: Bug > Components: Appenders > Affects Versions: 2.0.10 > Environment: alpine linux 3.1.8-alpine3.12, dotnet core 3.1. > Reporter: Robert May > Priority: Blocker > > Update: I've also tested this with 2.0.11 and it still doesn't work > correctly. > We have unit tests that are testing to ensure that certain log errors and > warnings are output. We do this by setting up a memory appender in our test > initialize. > After upgrading to 2.0.10, memory appender never has any events. We tried > both PopAllEvents and GetEvents and neither return any events. > Everything works fine on Windows, but doesn't work on Linux or Mac. > Initialization code: > {{var repo = LogManager.GetRepository(typeof(xxxx).Assembly);}} > {{this.LogAppender = new MemoryAppender();}} > {{BasicConfigurator.Configure(repo, this.LogAppender);}} -- This message was sent by Atlassian Jira (v8.3.4#803005)