On 2018-01-20, Dominik Psenner wrote:

> On 20 Jan 2018 7:27 p.m., "Stefan Bodewig" <[email protected]> wrote:

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

> I see. I wonder why the build worked on ci.

because there is no build step for compile-net-2.0 :-)

I'll try to add one.

> 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.

The build ends with

,----
| Could not update commit status, please check if your scan credentials belong 
to a member of the organization or a collaborator of the repository and 
repo:status scope is selected
| 
| ERROR: script returned exit code 1
| Finished: FAILURE
`----

I have no idea what this means.

>> 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
>> test".

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

Then maybe my fear that the test pass on Windows but fail on Linux is
warranted. In any case it doesn't necessarily need to stop us from
building the 2.0.9 release as the test used to pass on my Windows bix
and they still do.

Stefan

Reply via email to