logging-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominik Psenner <dpsen...@gmail.com>
Subject Re: [log4net] exclusive lock on .NET Core 1.x and Linux
Date Sun, 21 Jan 2018 10:48:50 GMT
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 Bodewig" <bodewig@apache.org> wrote:

> 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/
> problem/56318/the-active-test-run-was-aborted-reason-unable-to-c.html
> indicates there is no way for us to avoid the crashed test runner or to
> get decent information about which test is responsible for the crash (we
> may be able to see somthing if we increase verbosity again, oh my).
> There are reports of this problem being fixed in .NET Core 2.x but that
> won't help us.
> Unfortunately it doesn't seem to happen on the local docker image I've
> created for my own tests. This really is frustrating.
> Stefan

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message