Tests are failing on Linux for DesktopCLR #865

ghost · 2017-06-14T21:57:44Z

Description

I am trying to solve the following issues:

castleproject/Windsor#243
~~nunit/nunit3-vs-adapter#324~~

Steps to reproduce

Please clone the repro at: https://github.com/fir3pho3nixx/nunit-adapter-vs-xunit
Run build.sh on linux.

Expected behavior

I don't get System.ComponentModel.Win32Exception: Permission denied

Actual behavior

I get System.ComponentModel.Win32Exception: Permission denied

Environment

.NET Command Line Tools (1.0.1)

Product Information:
 Version:            1.0.1
 Commit SHA-1 hash:  005db40cd1

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  16.04
 OS Platform: Linux
 RID:         ubuntu.16.04-x64
 Base Path:   /usr/share/dotnet/sdk/1.0.1

The text was updated successfully, but these errors were encountered:

Faizan2304 · 2017-06-15T12:36:44Z

@Fir3pho3nixx dotnet test doesn't have capability to run Desktop test on Linux machine. We are tracking the work to enable it on Linux here

ghost · 2017-06-15T12:39:42Z

My issue is slightly different. I am using the targeting pack for net461 with framework override. Also my project builds fine. No mono from what I can tell unless that is what is happening under the covers.

codito · 2017-06-16T02:19:35Z

Interesting issue. The framework override is here in the project.

dotnet test is trying to spawn testhost.exe for net46 target. PE executables are not natively registered in linux machines, the OS throws when we're attempting to launch something that it doesn't recognize as an executable. We need to launch testhost.exe with a CLR host (mono in this case).

In #851 we're fixing running testhost.exe within mono. I will raise a follow up PR to spawn mono testhost.exe for net46 tests.

codito · 2017-06-17T03:04:25Z

Fix for this is in latest commit to #851

ghost · 2017-06-19T18:20:36Z

@codito - thank you for the quick response to this. I really appreciate it, it will clean up our build process and allow us to move off NUnitLite.

JoseFMP · 2017-06-23T06:05:47Z

Great that it will be fixed! Any work around in the mean time?

ghost · 2017-06-23T06:57:14Z

@jose-cf

Yes, you can temporarily use NUnitLite.

Make sure you set AppendRuntimeIdentifierToOutputPath to false.

Set your project type to exe.

Grab the nunit lite package.

Add Program.cs to your test project.

Then run it with NUnit options.

JoseFMP · 2017-06-23T07:38:20Z

Ok. In that case it looks simpler to do:

mkdir xunitTestRunner
sudo chmod a+rw xunitTestRunner
nuget install xunit.runner.console -Version 2.2.0  -OutputDirectory $PWD/xunitTestRunner
find ./artifacts/test -name "*Test.dll"       -print0 | xargs -0 -n1 mono xunitTestRunner/xunit.runner.console.2.2.0/tools/xunit.console.exe

I hope dotnet test will fix soon.

ghost · 2017-06-23T07:39:39Z

Agreed, our tests are all in NUnit though :/

ghost · 2017-06-23T22:00:03Z

I hope dotnet test will fix soon.

That is exactly what this team is fixing with this issue. Please see #851. It is now in the 15.3 milestone.

ghost · 2017-06-27T22:04:35Z

@codito - Can we get this bundled into the current preview? Would be happy to be a test subject.

codito · 2017-06-30T12:34:10Z

@Fir3pho3nixx we're working on getting this into a dotnet-cli dev build (hopefully early next week).

ghost · 2017-07-02T18:19:43Z

@codito - Cool, ping back on this issue, I will have an answer for you the next day.

codito · 2017-07-07T07:26:51Z

@Fir3pho3nixx please try out the latest dotnet-cli dev builds: https://github.com/dotnet/cli#installers-and-binaries.

In local testing, we hit nunit/nunit3-vs-adapter#327, the workaround is to use dev builds of nunit adapter:

Use nuget package source: https://www.myget.org/F/nunit/api/v3/index.json
Use Nunit3TestAdapter version 3.8.0-dev-00491
Disable source information collection as follows: dotnet test -- RunConfiguration.CollectSourceInformation=false

ghost · 2017-07-07T12:47:18Z

I am on holiday for a week and will be able to look at this when I get back. Thanks for pinging back! 👍

ghost · 2017-07-18T18:31:42Z

After updating to the nightly build I have found other issues. Please note, this was before I changed Castle.Core to use the dev build of the NUnit adapter.

dotnet restore

Appears to be functioning correctly; when I run the following commands

dotnet restore ./buildscripts/BuildScripts.csproj -s https://dotnet.myget.org/F/dotnet-core/api/v3/index.json
dotnet restore ./src/Castle.Core/Castle.Core.csproj
dotnet restore ./src/Castle.Services.Logging.log4netIntegration/Castle.Services.Logging.log4netIntegration.csproj
dotnet restore ./src/Castle.Services.Logging.NLogIntegration/Castle.Services.Logging.NLogIntegration.csproj
dotnet restore ./src/Castle.Services.Logging.SerilogIntegration/Castle.Services.Logging.SerilogIntegration.csproj
dotnet restore ./src/Castle.Core.Tests/Castle.Core.Tests.csproj

I get the following output:

Restore completed in 44.44 ms for /home/gavin/code/Core/buildscripts/BuildScripts.csproj.
  Restore completed in 25.53 ms for /home/gavin/code/Core/src/Castle.Core/Castle.Core.csproj.
  Restore completed in 22.53 ms for /home/gavin/code/Core/src/Castle.Core/Castle.Core.csproj.
  Restore completed in 2.93 ms for /home/gavin/code/Core/src/Castle.Services.Logging.log4netIntegration/Castle.Services.Logging.log4netIntegration.csproj.
  Restore completed in 34.41 ms for /home/gavin/code/Core/src/Castle.Core/Castle.Core.csproj.
  Restore completed in 1 ms for /home/gavin/code/Core/src/Castle.Services.Logging.NLogIntegration/Castle.Services.Logging.NLogIntegration.csproj.
  Restore completed in 178.18 ms for /home/gavin/code/Core/src/Castle.Core/Castle.Core.csproj.
  Restore completed in 17.11 ms for /home/gavin/code/Core/src/Castle.Services.Logging.SerilogIntegration/Castle.Services.Logging.SerilogIntegration.csproj.
  Restore completed in 54.3 ms for /home/gavin/code/Core/src/Castle.Core.Tests/Castle.Core.Tests.csproj.
  Restore completed in 3.48 ms for /home/gavin/code/Core/src/Castle.Core/Castle.Core.csproj.
  Restore completed in 3.78 ms for /home/gavin/code/Core/src/Castle.Services.Logging.NLogIntegration/Castle.Services.Logging.NLogIntegration.csproj.
  Restore completed in 2.12 ms for /home/gavin/code/Core/src/Castle.Services.Logging.SerilogIntegration/Castle.Services.Logging.SerilogIntegration.csproj.
  Restore completed in 0.71 ms for /home/gavin/code/Core/src/Castle.Services.Logging.log4netIntegration/Castle.Services.Logging.log4netIntegration.csproj.

dotnet build

Also appears to function correctly

dotnet build ./src/Castle.Core.Tests/Castle.Core.Tests.csproj /p:Configuration=Release || exit 1

I get the following output:

Microsoft (R) Build Engine version 15.3.406.54721 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Castle.Core -> /home/gavin/code/Core/src/Castle.Core/bin/Release/net45/Castle.Core.dll
  Castle.Services.Logging.log4netIntegration -> /home/gavin/code/Core/src/Castle.Services.Logging.log4netIntegration/bin/Release/net45/Castle.Services.Logging.log4netIntegration.dll
  Castle.Services.Logging.NLogIntegration -> /home/gavin/code/Core/src/Castle.Services.Logging.NLogIntegration/bin/Release/net45/Castle.Services.Logging.NLogIntegration.dll
  Castle.Services.Logging.SerilogIntegration -> /home/gavin/code/Core/src/Castle.Services.Logging.SerilogIntegration/bin/Release/net45/Castle.Services.Logging.SerilogIntegration.dll
  Castle.Core.Tests -> /home/gavin/code/Core/src/Castle.Core.Tests/bin/Release/net461/Castle.Core.Tests.exe
  Castle.Core -> /home/gavin/code/Core/src/Castle.Core/bin/Release/netstandard1.3/Castle.Core.dll
  Castle.Services.Logging.SerilogIntegration -> /home/gavin/code/Core/src/Castle.Services.Logging.SerilogIntegration/bin/Release/netstandard1.3/Castle.Services.Logging.SerilogIntegration.dll
  Castle.Core.Tests -> /home/gavin/code/Core/src/Castle.Core.Tests/bin/Release/netcoreapp1.1/Castle.Core.Tests.dll

Running net461 tests as a console app

This is where the problems start creeping in. Using the following command:

./src/Castle.Core.Tests/bin/Release/net461/Castle.Core.Tests.exe --result=DesktopClrTestResults.xml;format=nunit3

I get the following output:

./build.sh: line 48: ./src/Castle.Core.Tests/bin/Release/net461/Castle.Core.Tests.exe: Permission denied

Running the dotnet core tests using dotnet test

I also now have problems. Running the following command:

dotnet ./src/Castle.Core.Tests/bin/Release/netcoreapp1.1/Castle.Core.Tests.dll --result=NetCoreClrTestResults.xml;format=nunit3

I get the following output:

It was not possible to find any compatible framework version
The specified framework 'Microsoft.NETCore.App', version '1.1.2' was not found.
  - Check application dependencies and target a framework version installed at:
      /
  - Alternatively, install the framework version '1.1.2'.

ghost · 2017-07-18T18:35:41Z

Here is some more info about my environment:

dotnet --version

2.1.0-preview1-006784

mono --version

Mono JIT compiler version 5.0.1.1 (2017-02/5077205 Thu May 25 09:19:18 UTC 2017)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           __thread
	SIGSEGV:       altstack
	Notifications: epoll
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug 
	LLVM:          supported, not enabled.
	GC:            sgen (concurrent by default)

lsb_release -a

Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.1 LTS
Release:	16.04
Codename:	xenial

Not sure what has happened here but it feels like either I am out of date and am in dire need of upgrading or things have gone slightly backwards.

If there is anything you guys need please let me know.

codito · 2017-07-20T06:32:24Z

@Fir3pho3nixx is there a branch I can look into for the source? I can try out at my end and suggest if there are any changes.

It should be possible to run both desktop and netcore tests with following command:

> dotnet test ./src/Castle.Core.Tests/Castle.Core.Tests.csproj /p:Configuration=Release || exit 1

ghost · 2017-07-20T07:34:02Z

@codito Thanks for getting back to me. I agree that this command should be used for both, however before I even upgraded the project to do this I was having problems with my current configuration so held off.

Our current working build is on master @ https://github.com/castleproject/Core. The build script is here and our TravisCI build configuration is here.

You can see from the above I upgraded mono and the dotnet cli which started causing the failures.

codito · 2017-07-21T15:11:39Z

Running net461 tests

In Ubuntu, exe files are not treated as executables by default, also the OS doesn't know that it has to invoke mono to run these. Using following command runs the tests:

mono ./src/Castle.Core.Tests/bin/Release/net461/Castle.Core.Tests.exe --result=DesktopClrTestResults.xml;format=nunit3

Running netcoreapp1.1 tests

The error says .net core shared runtime 1.1.2 is not installed. With the dotnet latest dev builds it doesn't come packaged with SDK. The tests ran once I installed it separately from https://github.com/dotnet/core/blob/master/release-notes/download-archives/1.1.2-download.md (see Runtime Installer for the OS).

ghost · 2017-07-21T15:21:14Z

In Ubuntu, exe files are not treated as executables by default, also the OS doesn't know that it has to invoke mono to run these. Using following command runs the tests:

That is curious, as the binary file used to be generated with a 'x' attr. No problems, going to be converting it all over anyway.

Many thanks for taking the time to review. Will close this out once I have replicated your recommendations successfully.

codito · 2017-07-21T15:30:43Z

In Ubuntu, exe files are not treated as executables by default, also the OS doesn't know that it has to invoke mono to run these. Using following command runs the tests:

That is curious, as the binary file used to be generated with a 'x' attr. No problems, going to be converting it all over anyway.

Mono docs mention it is possible to use binfmt on linux to register exe with mono. It recommends using a wrapper script for portability though :)

codito · 2017-08-02T02:25:03Z

@Fir3pho3nixx just checking in, were you able to run the tests in linux?

ghost · 2017-08-02T09:37:02Z

~~Not yet, will get to it this weekend.~~ This week.

Faizan2304 · 2017-09-11T14:39:12Z

@Fir3pho3nixx : If you don't have any open question here then can I close this issue?

ghost · 2017-09-11T14:41:38Z

My apologies, meant to close this ages ago. Thank everyone!

UncleFirefox · 2017-09-22T11:44:34Z

Hi, will this be fixed anytime soon in the official release? Thanks!

codito added enhancement exp: cli labels Jun 16, 2017

codito self-assigned this Jun 16, 2017

codito added this to the 15.3 milestone Jun 16, 2017

ghost mentioned this issue Jun 19, 2017

Use the latest NUnitTestAdapter for running tests (3.8.0-alpha1) castleproject/Windsor#243

Closed

ghost mentioned this issue Jun 23, 2017

Proxy creation fails where method parameters carry certain modopt combinations castleproject/Core#277

Closed

codito modified the milestones: 15.5 (Sprint 121), 15.3 Jul 7, 2017

Faizan2304 modified the milestones: 15.5 (Sprint 122), 15.5 (Sprint 121) Aug 1, 2017

ghost closed this as completed Sep 11, 2017

jindraivanek mentioned this issue Sep 23, 2017

travis CI updated to use dotnet CLI jack-pappas/ExtCore#28

Merged

This issue was closed.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Tests are failing on Linux for DesktopCLR #865

Tests are failing on Linux for DesktopCLR #865

ghost commented Jun 14, 2017 •

edited by ghost

Loading

Faizan2304 commented Jun 15, 2017

ghost commented Jun 15, 2017

codito commented Jun 16, 2017 •

edited

Loading

codito commented Jun 17, 2017

ghost commented Jun 19, 2017

JoseFMP commented Jun 23, 2017

ghost commented Jun 23, 2017 •

edited by ghost

Loading

JoseFMP commented Jun 23, 2017

ghost commented Jun 23, 2017

ghost commented Jun 23, 2017

ghost commented Jun 27, 2017

codito commented Jun 30, 2017

ghost commented Jul 2, 2017

codito commented Jul 7, 2017

ghost commented Jul 7, 2017

ghost commented Jul 18, 2017 •

edited by ghost

Loading

ghost commented Jul 18, 2017 •

edited by ghost

Loading

codito commented Jul 20, 2017 •

edited

Loading

ghost commented Jul 20, 2017

codito commented Jul 21, 2017

ghost commented Jul 21, 2017

codito commented Jul 21, 2017

codito commented Aug 2, 2017

ghost commented Aug 2, 2017 •

edited by ghost

Loading

Faizan2304 commented Sep 11, 2017

ghost commented Sep 11, 2017

UncleFirefox commented Sep 22, 2017 •

edited

Loading

Tests are failing on Linux for DesktopCLR #865

Tests are failing on Linux for DesktopCLR #865

Comments

ghost commented Jun 14, 2017 • edited by ghost Loading

Description

Steps to reproduce

Expected behavior

Actual behavior

Environment

Faizan2304 commented Jun 15, 2017

ghost commented Jun 15, 2017

codito commented Jun 16, 2017 • edited Loading

codito commented Jun 17, 2017

ghost commented Jun 19, 2017

JoseFMP commented Jun 23, 2017

ghost commented Jun 23, 2017 • edited by ghost Loading

JoseFMP commented Jun 23, 2017

ghost commented Jun 23, 2017

ghost commented Jun 23, 2017

ghost commented Jun 27, 2017

codito commented Jun 30, 2017

ghost commented Jul 2, 2017

codito commented Jul 7, 2017

ghost commented Jul 7, 2017

ghost commented Jul 18, 2017 • edited by ghost Loading

dotnet restore

dotnet build

Running net461 tests as a console app

Running the dotnet core tests using dotnet test

ghost commented Jul 18, 2017 • edited by ghost Loading

codito commented Jul 20, 2017 • edited Loading

ghost commented Jul 20, 2017

codito commented Jul 21, 2017

Running net461 tests

Running netcoreapp1.1 tests

ghost commented Jul 21, 2017

codito commented Jul 21, 2017

codito commented Aug 2, 2017

ghost commented Aug 2, 2017 • edited by ghost Loading

Faizan2304 commented Sep 11, 2017

ghost commented Sep 11, 2017

UncleFirefox commented Sep 22, 2017 • edited Loading

ghost commented Jun 14, 2017 •

edited by ghost

Loading

codito commented Jun 16, 2017 •

edited

Loading

ghost commented Jun 23, 2017 •

edited by ghost

Loading

ghost commented Jul 18, 2017 •

edited by ghost

Loading

ghost commented Jul 18, 2017 •

edited by ghost

Loading

codito commented Jul 20, 2017 •

edited

Loading

ghost commented Aug 2, 2017 •

edited by ghost

Loading

UncleFirefox commented Sep 22, 2017 •

edited

Loading