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] release 2.0.9
Date Sat, 20 Jan 2018 18:41:39 GMT
On 20 Jan 2018 7:27 p.m., "Stefan Bodewig" <bodewig@apache.org> wrote:

On 2018-01-20, Dominik Psenner wrote:

> On 20 Jan 2018 6:47 p.m., "Stefan Bodewig" <bodewig@apache.org> wrote:

>> On 2018-01-15, Dominik Psenner wrote:
>>> 2018-01-15 10:22 GMT+01:00 Stefan Bodewig <bodewig@apache.org>:

>>>> There still are lots of version conflicts that we probably want to
>>>> reolve first. Unfortunately I have no clue how to resolve them
>>>> so that we figure out the minimal versions required to make things work
>>>> on .NET Standard 1.3.

>>> That's great news. Please try the feature/cd-pipeline branch, there I
>>> may have already fixed all of this. But since this does not work on CI
>>> it's not yet merged into develop.

>> After merging the fix to the NAnt build so that .NET 2.0 compilation
>> works I've been able to build that branch. The test result on Windows:

>> ,----
>> | NUnit Adapter Test execution complete
>> |
>> | Total tests: 91. Passed: 85. Failed: 0. Skipped: 6.
>> | Test Run Successful.
>> | Test execution time: 3.8648 Seconds
>> `----
>> So it seems the test errors you see in CI don't happen on my Win7 build
>> VM.

> The .net 2.0 tests should not be broken, as far as I am aware of. Do you
> mean netstandard-2.0?


Building .NET 2.0 (not standard or core, good old .NET framework) was

I see. I wonder why the build worked on ci. Btw, have you noticed that the
head of develop failed in ci? I'm currently on my phone only and therefore
cant figure out why.

> CI does fail with testing netstandard1.3, which would be the target
> runtests-netstandard-1.3. Were you able to run the tests against all
> targetted frameworks?

Not sure what "all targetted" frameworks means. The quote above is from
running the .NET Standard tests using .NET Core SDK 1.1.7 on Win7. I
tested this by changing into the log4net.tests dir and running "dotnet

That's roughly what the runtests-netstandard-1.3 target does, too.

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