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

Notification

Icon
Error

Visual Studio 16.8 RTM - NCrunch Error
upper
#1 Posted : Tuesday, November 10, 2020 7:33:39 PM(UTC)
Rank: Member

Groups: Registered
Joined: 9/21/2016(UTC)
Posts: 24
Location: Austria

Thanks: 4 times
Was thanked: 6 time(s) in 6 post(s)
After updating to VS 2019 16.8 (Enterprise) NCrunch only shows errors (we have a asp.net core 3.1 solution, about 40 c# projects) --> Full Framework Solutions (.net 4.7.2) seems to working fine in 16.8)

Restarting VS, restarting NCrunch (deleting the .obj folder or the .vs folder) does not solve the problem, also setting the instrumentation mode to legacy does not fix the problem.

We are using MSTest v2.

FYI: The VS test runner as well as the R# test runner are still working fine.

Going back to VS 2019 16.7.x fixes the problem.

Update: I also submited a bug via Visual Studio.


[20:31:23.3318-UI-1] getWindow for nCrunch.VSIntegration2010.TestsToolWindowPane
[20:31:50.2569-UI-1] getWindow for nCrunch.VSIntegration2010.TestsToolWindowPane
ENGINE - [20:31:51.0568-LocalTestExecutionTask-36] ERROR (Internal): nCrunch.TaskRunner.Ipc.IpcConnectionClosedException: The connection has been closed
at nCrunch.TaskRunner.Ipc.Fast.IpcReader.Initialise()
at nCrunch.TaskRunner.Ipc.Fast.IpcStream.Connect(String ipcName, Boolean isHost)
at nCrunch.TaskRunner.Ipc.Fast.FastIpcClient.Connect(String ipcName)
at nCrunch.Core.ProcessManagement.DefaultProcessLoader.ConnectToProcess(ExternalProcess externalProcess, ProcessLoadParameters parameters, Action`1 outOfBandMessageHandler)
at nCrunch.Core.ProcessManagement.ExternalProcessManager..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Core.ProcessManagement.ExternalProcessManager.(EffectiveProcessorArchitecture , ProcessLoadParameters )

ENGINE - [20:31:51.0588-LocalTestExecutionTask-36] 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.TestExecutionTaskLogic.DoProcessTaskAndReturnSuccessFlag()
ENGINE - [20:31:51.4368-LocalTestExecutionTask-43] ERROR (Internal): nCrunch.TaskRunner.Ipc.IpcConnectionClosedException: The connection has been closed
at nCrunch.TaskRunner.Ipc.Fast.IpcReader.Initialise()
at nCrunch.TaskRunner.Ipc.Fast.IpcStream.Connect(String ipcName, Boolean isHost)
at nCrunch.TaskRunner.Ipc.Fast.FastIpcClient.Connect(String ipcName)
at nCrunch.Core.ProcessManagement.DefaultProcessLoader.ConnectToProcess(ExternalProcess externalProcess, ProcessLoadParameters parameters, Action`1 outOfBandMessageHandler)
at nCrunch.Core.ProcessManagement.ExternalProcessManager..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TrackActivity(String name, Action activity)
at nCrunch.Core.ProcessManagement.ExternalProcessManager.(EffectiveProcessorArchitecture , ProcessLoadParameters )


Detailed log:
https://drive.google.com...qU3jvtY/view?usp=sharing
UppSol
#2 Posted : Tuesday, November 10, 2020 8:38:15 PM(UTC)
Rank: Member

Groups: Registered
Joined: 3/21/2019(UTC)
Posts: 29
Location: Austria

Thanks: 16 times
Was thanked: 6 time(s) in 6 post(s)
Btw we are using the latest NCrunch version (4.4.0.12)
michaelkroes
#3 Posted : Tuesday, November 10, 2020 8:45:08 PM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 224
Location: Netherlands

Thanks: 98 times
Was thanked: 50 time(s) in 48 post(s)
Thanks for reporting this to us. We're looking into it.
1 user thanked michaelkroes for this useful post.
UppSol on 11/10/2020(UTC)
UppSol
#4 Posted : Wednesday, November 11, 2020 3:49:44 PM(UTC)
Rank: Member

Groups: Registered
Joined: 3/21/2019(UTC)
Posts: 29
Location: Austria

Thanks: 16 times
Was thanked: 6 time(s) in 6 post(s)
michaelkroes;15023 wrote:
Thanks for reporting this to us. We're looking into it.


I've seen Remco tweeted a release is prepared that will work with .net 5, will this bug also covered by this fix?
Br
michaelkroes
#5 Posted : Wednesday, November 11, 2020 4:39:48 PM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 224
Location: Netherlands

Thanks: 98 times
Was thanked: 50 time(s) in 48 post(s)
upper
#6 Posted : Wednesday, November 11, 2020 4:47:13 PM(UTC)
Rank: Member

Groups: Registered
Joined: 9/21/2016(UTC)
Posts: 24
Location: Austria

Thanks: 4 times
Was thanked: 6 time(s) in 6 post(s)
michaelkroes
#7 Posted : Wednesday, November 11, 2020 4:56:13 PM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 224
Location: Netherlands

Thanks: 98 times
Was thanked: 50 time(s) in 48 post(s)
Sorry to hear that.

The log you supplied shows the test execution process dying. Would you mind checking the event viewer to see if there's any extra information about the crashing process?

If there's nothing there would you mind trying to create a small test project?

In the mean time I'll investigate some more on our end.
upper
#8 Posted : Wednesday, November 11, 2020 5:02:42 PM(UTC)
Rank: Member

Groups: Registered
Joined: 9/21/2016(UTC)
Posts: 24
Location: Austria

Thanks: 4 times
Was thanked: 6 time(s) in 6 post(s)
michaelkroes;15032 wrote:
Sorry to hear that.

The log you supplied shows the test execution process dying. Would you mind checking the event viewer to see if there's any extra information about the crashing process?

If there's nothing there would you mind trying to create a small test project?

In the mean time I'll investigate some more on our end.


There is nothing in the windows event log, here is a sample project: https://drive.google.com...ii6scl/view?usp=sharing

It only happens when I use a asp.net core web project :
Microsoft.NET.Sdk.Web


<Project Sdk="Microsoft.NET.Sdk.Web">

<PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
</PropertyGroup>


</Project>

When I use a non web project like so everything is working

<Project Sdk="Microsoft.NET.Sdk">

<PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
</PropertyGroup>


</Project>
michaelkroes
#9 Posted : Wednesday, November 11, 2020 5:05:16 PM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 224
Location: Netherlands

Thanks: 98 times
Was thanked: 50 time(s) in 48 post(s)
Thanks! I’ll give that a try and report back.
upper
#10 Posted : Wednesday, November 11, 2020 5:08:08 PM(UTC)
Rank: Member

Groups: Registered
Joined: 9/21/2016(UTC)
Posts: 24
Location: Austria

Thanks: 4 times
Was thanked: 6 time(s) in 6 post(s)
michaelkroes;15034 wrote:
Thanks! I’ll give that a try and report back.


Please have look at the previous post, I found the reason, it <Project Sdk="Microsoft.NET.Sdk.Web">
br
michaelkroes
#11 Posted : Wednesday, November 11, 2020 5:10:46 PM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 224
Location: Netherlands

Thanks: 98 times
Was thanked: 50 time(s) in 48 post(s)
Just to clarify, you do expect that sdk to work with NCrunch right? Because it works with VS an R#. Vs 2019 had some changes before in this area. Our old test case seem to pass.
upper
#12 Posted : Wednesday, November 11, 2020 5:13:28 PM(UTC)
Rank: Member

Groups: Registered
Joined: 9/21/2016(UTC)
Posts: 24
Location: Austria

Thanks: 4 times
Was thanked: 6 time(s) in 6 post(s)
michaelkroes;15036 wrote:
Just to clarify, you do expect that sdk to work with NCrunch right? Because it works with VS an R#. Vs 2019 had some changes before in this area. Our old test case seem to pass.


Yes. <Project Sdk="Microsoft.NET.Sdk"> AND <Project Sdk="Microsoft.NET.Sdk.Web"> should work, it was working more or less I can remember and stopped yesterday after installing VS 2019 16.8.

br


michaelkroes
#13 Posted : Wednesday, November 11, 2020 5:14:13 PM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 224
Location: Netherlands

Thanks: 98 times
Was thanked: 50 time(s) in 48 post(s)
Awesome. I’ll investigate.
upper
#14 Posted : Wednesday, November 11, 2020 5:16:48 PM(UTC)
Rank: Member

Groups: Registered
Joined: 9/21/2016(UTC)
Posts: 24
Location: Austria

Thanks: 4 times
Was thanked: 6 time(s) in 6 post(s)
michaelkroes;15038 wrote:
Awesome. I’ll investigate.


thank you very much!

Btw. I also tried to reinstalled the .net sdk without luck.
michaelkroes
#15 Posted : Wednesday, November 11, 2020 6:24:57 PM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 224
Location: Netherlands

Thanks: 98 times
Was thanked: 50 time(s) in 48 post(s)
I see from the solution cache that you had an error with the solution. But when I rebuild it on two different machines it works for me. I'm going to consult with Remco and see what we can try next.
upper
#16 Posted : Wednesday, November 11, 2020 6:25:55 PM(UTC)
Rank: Member

Groups: Registered
Joined: 9/21/2016(UTC)
Posts: 24
Location: Austria

Thanks: 4 times
Was thanked: 6 time(s) in 6 post(s)
michaelkroes;15040 wrote:
I see from the solution cache that you had an error with the solution. But when I rebuild it on two different machines it works for me. I'm going to consult with Remco and see what we can try next.

thx
1 user thanked upper for this useful post.
michaelkroes on 11/11/2020(UTC)
upper
#17 Posted : Wednesday, November 11, 2020 7:01:27 PM(UTC)
Rank: Member

Groups: Registered
Joined: 9/21/2016(UTC)
Posts: 24
Location: Austria

Thanks: 4 times
Was thanked: 6 time(s) in 6 post(s)
upper;15041 wrote:
michaelkroes;15040 wrote:
I see from the solution cache that you had an error with the solution. But when I rebuild it on two different machines it works for me. I'm going to consult with Remco and see what we can try next.

thx


I found the problem:
I removed the 2019 16.8 Preview Version of VS than I repaired NCrunch (using the NCrunch Installer) and now everything is working fine again. --> I really like MS ;)

Sorry for wasting your time!
1 user thanked upper for this useful post.
michaelkroes on 11/11/2020(UTC)
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.101 seconds.