Why Log4Net's standard output \n per character?

We run unit tests using nunit runner in team city. Our unit test library 'test.dll' has log4net integrated and writes to standard output as default whenever there is an exception executing a test. The problem is that the logs are being spitted to the team city build log with '\n'  appended to every character of the exception message.

Please find attached the build log and let us know if something needs to be configured in team city. Also for the same reason the team city logger is timing out (see bottom of the log file for more details).

PS: After we redirected the Log4Net's output to a database they are not timing out any more and running fine.



Attachment(s):
IncentiveManager.QA_Integration_Integration_Tests_-_Sql_Server_2005_16847_134_.log.zip
2 comments
Comment actions Permalink

Hi

This is the issue reported in TW-18113, please watch for it.

Thanks
Michael

0
Comment actions Permalink

Hello,

You have the same issue as discribed in http://youtrack.jetbrains.net/issue/TW-13990,
Please vote for it. It was fixed for 7.0

0

Please sign in to leave a comment.