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

Notification

Icon
Error
NCrunch fails to start debugging tests
Options
Previous Topic Next Topic
offset123
#1 Posted : Friday, March 17, 2017 5:52:46 PM(UTC)
Rank: Member

Groups: Registered
Joined: 8/24/2015(UTC)
Posts: 16
Location: Slovenia

Was thanked: 2 time(s) in 2 post(s)
Since the recent releases (so in the last week or so) I've noticed NCrunch becoming unstable when it comes to running tests through a debugger. I'm using the latest version (3.6.0.2) on two different computers and the problems are on both.
I'm using .NET 4.6.1.
Instead of starting the debugger, NCrunch reports errors like:

Code:
[18:41:28.5651-EventReader-71] Publishing Event: [DebuggerDetachRequestedEvent:20744]
[18:41:28.5661-EventReader-71] Event [DebuggerDetachRequestedEvent:20744] is being published on thread UIThread to subscriber:  .
[18:41:28.5661-EventReader-71] Event [DebuggerDetachRequestedEvent:20744] is being published on thread CoreThread to subscriber: SharedEventPump.
[18:41:28.5661-Core-367] Event [DebuggerDetachRequestedEvent:20744] is being processed on Core thread with subscriber: SharedEventPump.
ENGINE - Process 20744: 18:41:28.5551 [6] - Running 1 tests using executor: nCrunch.Module.NUnit3.Integration.NUnit3FrameworkRuntimeEnvironment
ENGINE - Process 20744: 18:41:28.5621 [10] - System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
ENGINE - Process 20744:    at nCrunch.TestRuntime.Win32.CloseHandle(IntPtr handle)
[18:41:28.5661-EventReader-71] Publishing Event: [ErrorEvent:[Error:
Context: (global)
Category: Internal
Message: System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
   at nCrunch.TestRuntime.Win32.CloseHandle(IntPtr handle)
   at nCrunch.TestRuntime.SharedMemoryExecutionDataRecorder.Dispose()
   at nCrunch.TestExecution.TestRunnerThread.()
   at nCrunch.TestExecution.TestRunnerThread.()
Details: 
]]
ENGINE - Process 20744:    at nCrunch.TestRuntime.SharedMemoryExecutionDataRecorder.Dispose()
ENGINE - Process 20744:    at nCrunch.TestExecution.TestRunnerThread.()
[18:41:28.5661-EventReader-71] Event [ErrorEvent:[Error:
Context: (global)
Category: Internal
Message: System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
   at nCrunch.TestRuntime.Win32.CloseHandle(IntPtr handle)
   at nCrunch.TestRuntime.SharedMemoryExecutionDataRecorder.Dispose()
   at nCrunch.TestExecution.TestRunnerThread.()
   at nCrunch.TestExecution.TestRunnerThread.()
Details: 
]] is being published on thread CoreThread to subscriber: ErrorHandler.


Let me know if you need full logs.
Back to top
Remco
#2 Posted : Friday, March 17, 2017 10:46:28 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 960 times
Was thanked: 1290 time(s) in 1196 post(s)
Thanks for sharing this problem.

Although it doesn't appear the same way for me, I've seen some similar issues around this component lately. I have some ideas on things I can try.

I'll try to get a speculative fix included for this in the next release.
Back to top
offset123
#3 Posted : Sunday, March 19, 2017 10:58:23 AM(UTC)
Rank: Member

Groups: Registered
Joined: 8/24/2015(UTC)
Posts: 16
Location: Slovenia

Was thanked: 2 time(s) in 2 post(s)
Remco;10003 wrote:
Thanks for sharing this problem.

Although it doesn't appear the same way for me, I've seen some similar issues around this component lately. I have some ideas on things I can try.

I'll try to get a speculative fix included for this in the next release.


Do you have any estimates on when the next version will be released? Right now using NCrunch is a pain (and the problem with file changes not being detected is still occurring).
Back to top
Remco
#4 Posted : Sunday, March 19, 2017 12:06:16 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 960 times
Was thanked: 1290 time(s) in 1196 post(s)
offset123;10021 wrote:

Do you have any estimates on when the next version will be released? Right now using NCrunch is a pain (and the problem with file changes not being detected is still occurring).


Sorry, I can't make any promises on this right now. Things have honestly gone completely crazy with the VS2017/.NETCore release. I'll try to get this out when things have settled down a bit.
Back to top
offset123
#5 Posted : Sunday, March 19, 2017 2:32:50 PM(UTC)
Rank: Member

Groups: Registered
Joined: 8/24/2015(UTC)
Posts: 16
Location: Slovenia

Was thanked: 2 time(s) in 2 post(s)
Remco;10024 wrote:

Sorry, I can't make any promises on this right now. Things have honestly gone completely crazy with the VS2017/.NETCore release. I'll try to get this out when things have settled down a bit.


Is it possible to downgrade NCrunch from v3.6 to v3.3 without losing the existing configurations? I don't really need VS2017 and Core stuff.
Back to top
Remco
#6 Posted : Sunday, March 19, 2017 10:55:05 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 960 times
Was thanked: 1290 time(s) in 1196 post(s)
offset123;10028 wrote:

Is it possible to downgrade NCrunch from v3.6 to v3.3 without losing the existing configurations? I don't really need VS2017 and Core stuff.


Yes, I believe so. I haven't personally tested this, but in theory v3.3 should be forwards compatible with v3.6 configuration files.
Back to top
offset123
#7 Posted : Tuesday, March 21, 2017 10:18:46 AM(UTC)
Rank: Member

Groups: Registered
Joined: 8/24/2015(UTC)
Posts: 16
Location: Slovenia

Was thanked: 2 time(s) in 2 post(s)
Remco;10032 wrote:
offset123;10028 wrote:

Is it possible to downgrade NCrunch from v3.6 to v3.3 without losing the existing configurations? I don't really need VS2017 and Core stuff.


Yes, I believe so. I haven't personally tested this, but in theory v3.3 should be forwards compatible with v3.6 configuration files.


I've uninstalled 3.6 and installed 3.3, the configuration seems to be OK and tests are running, so far so good.

In future, I suggest marking such high-risk releases with lot of new code and support for .NET Core in VS 2017 (which are in themselves unstable, to be fair) as "beta" and keeping the last stable one as a recommended download.
Back to top
Remco
#8 Posted : Friday, March 24, 2017 5:54:36 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 960 times
Was thanked: 1290 time(s) in 1196 post(s)
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.064 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download