Hi,
looks like thepipeline found a test failure and at first sight this should
not be possible with exclusive locks. So this is a hint towards a race
condition that exists in the rolling file appender. This failure could be
the root cause of several issues and unexpected behavior. I thought to
bring up this on the mailing list to have a bigger audience. Ideas?
Failed
log4net.Tests.Appender.RollingFileAppenderTest.TestExclusiveLockLocks
Stacktrace
MESSAGE:
Log contents is not
what is expected
String lengths are both 38. Strings differ at index 0.
Expected: "This is a message\nThis is a message 2\n"
But was: "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0This is a message 2\n"
-----------^
+++++++++++++++++++
STACK TRACE:
at
log4net.Tests.Appender.RollingFileAppenderTest.AssertFileEquals
(System.String filename, System.String contents) <0x41980f60 +
0x0007f> in <filename unknown>:0
at log4net.Tests.Appender.RollingFileAppenderTest.TestExclusiveLockLocks
() <0x41e7c150 + 0x002b7> in <filename unknown>:0
--
Dominik Psenner
