Re: [log4net] exclusive lock on .NET Core 1.x and Linux

2018-02-01 Thread Dominik Psenner
On 28 Jan 2018 11:45 a.m., "Stefan Bodewig" wrote: On 2018-01-21, Dominik Psenner wrote: > Sometimes it is possible to configure the test runner so that it runs in > process instead of spawning a new process. Would you like to investigate on > this? I don't see any such option. We could re-enab

Re: [log4net] exclusive lock on .NET Core 1.x and Linux

2018-01-28 Thread Stefan Bodewig
On 2018-01-21, Dominik Psenner wrote: > Sometimes it is possible to configure the test runner so that it runs in > process instead of spawning a new process. Would you like to investigate on > this? I don't see any such option. We could re-enable more detailed logging and try to figure out which

Re: [log4net] exclusive lock on .NET Core 1.x and Linux

2018-01-21 Thread Dominik Psenner
Sometimes it is possible to configure the test runner so that it runs in process instead of spawning a new process. Would you like to investigate on this? I had contact to Rob Prouse of the nunit developers. It might be a good idea to crosspost to nunit-discuss. On 21 Jan 2018 11:21 a.m., "Stefan

Re: [log4net] exclusive lock on .NET Core 1.x and Linux

2018-01-21 Thread Stefan Bodewig
On 2018-01-20, Stefan Bodewig wrote: > I have disabled the test conditionallly on Linux and the Jenkins build > now finishes the tests on Linux. But not reliably, there seems to be another test that crashes the test runner from time to time. https://developercommunity.visualstudio.com/content/pr

Re: [log4net] exclusive lock on .NET Core 1.x and Linux

2018-01-20 Thread Stefan Bodewig
On 2018-01-20, Stefan Bodewig wrote: > it looks as if exclusive locking didn't work properly for > RollingfileAppender on Linux for our NET Core tests. This has also > been true for the MONO_2_0 builds ages ago. I haven't checked whether > we are hitting a known limitation so far. https://github.