Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Can't run on .NETCoreApp 3.0
Options
Previous Topic Next Topic
WinMan
#1 Posted : Monday, October 14, 2019 6:28:08 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/27/2012(UTC)
Posts: 5
Location: Sweden
I got a new license for NCrunch but It doesn't start. The only thing I get is
An error occurred while analysing this project after it was built: NCrunch encountered an unexpected error occurred while building an environment to analyse an assembly: nCrunch.TaskRunner.Ipc.IpcConnectionClosedException: The connection has been closed
at nCrunch.Core.ProcessManagement.ExternalProcessManager.(EffectiveProcessorArchitecture , ProcessLoadParameters )
at nCrunch.Core.ProcessManagement.ExternalProcessManager.LoadExternalProcess(ProcessLoadParameters parameters, GridClientId client)
at nCrunch.Core.TestManagement.TestRunnerProcess..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Core.TestManagement.TestRunnerProcess.(Nullable`1 , FilePath , GridClientId , CustomVariable[] )
at nCrunch.Core.TestManagement.TestRunnerProcess..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Core.TestManagement.TestRunnerProcess.LoadTestRunnerProcessForProjectReturningProcessId(SnapshotComponent snapshotComponent, IList`1 componentsInProcess, TestFrameworkDescription[] testingFrameworks, Nullable`1 newProcessTag, FilePath solutionFilePath, GridClientId client, CustomVariable[] customEnvironmentVariables)
at nCrunch.Core.Processing.AnalysisTaskLogic.DoProcessTaskAndReturnSuccessFlag()

The project is a netcoreapp3.0
Back to top
Remco
#2 Posted : Monday, October 14, 2019 9:08:27 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi, thanks for sharing this issue.

Can you confirm whether you're running the latest version of NCrunch?

This looks like a problem was encountered while initialising the .NET Core environment. If you can submit a bug report after the failure, the log file may be able to yield some more information about why this is happening.
Back to top
WinMan
#3 Posted : Monday, October 14, 2019 9:22:08 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/27/2012(UTC)
Posts: 5
Location: Sweden
I'm running 3.31.0.3
Bug report submitted!
Back to top
Remco
#4 Posted : Tuesday, October 15, 2019 12:15:30 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Thanks for the bug report!

It looks like something in your test environment is causing the process to immediately terminate without providing any error information.

Are you able to produce this in a sample project of any kind? The problem may be specific to a dependency (i.e. Nuget, specific platform version).

Could you also check if you have any errors in your system event viewer?
Back to top
WinMan
#5 Posted : Wednesday, October 16, 2019 8:55:23 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/27/2012(UTC)
Posts: 5
Location: Sweden
Nope nothing in the event viewer. I have no trouble to run DotCover. No more hints where to look? We have a large project.
Back to top
Remco
#6 Posted : Thursday, October 17, 2019 12:26:35 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Unfortunately, with no stack trace or error information, we're reduced to deductively trying to find the source of the problem.

The first thing to try would be to see if you're able to create a new .NET core 3.0 test project on your machine using the same test framework as the one you're using in your larger solution.

Assuming this doesn't blow up, the next step would be to copy the XML content from your real-world test project's .proj file into your new dummy test project. The actual code (i.e. .cs files) probably isn't required to trigger this issue. It's almost certainly related to the packages and files being referenced, or other directives you have inside the .proj file.

You can continue to just move structural parts from your main solution into your dummy solution until the problem triggers. Again, I wouldn't worry about the source code itself, as the explosion here is happening during process initialisation - it hasn't even reached your code yet.
Back to top
WinMan
#7 Posted : Friday, October 18, 2019 6:49:13 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/27/2012(UTC)
Posts: 5
Location: Sweden
Solved. Not 100% sure what it was. My colleague changed the project so that we can build it on Linux and now it works.
Back to top
Remco
#8 Posted : Friday, October 18, 2019 11:08:21 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,144

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
WinMan;13958 wrote:
Solved. Not 100% sure what it was. My colleague changed the project so that we can build it on Linux and now it works.


I'm glad to hear! Let me know if it happens again and you can find a way to reproduce it.
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.049 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download