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

Notification

Icon
Error
How to determine what is causing NCrunch to die?
Options
Previous Topic Next Topic
samholder
#1 Posted : Monday, July 2, 2018 3:38:38 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/11/2012(UTC)
Posts: 94

Thanks: 28 times
Was thanked: 12 time(s) in 12 post(s)
we have some tests that have started failing randomly on the grid nodes (and occasionally locally) with this:

NCrunch was unable to retrieve a meaningful result from this test

looking around it seems that something is happening to cause the NCRunch process to die, and indeed locally when it happens I get a popup box that says the process has died.

Unfortunately its not always the same tests every time and is seemingly random.

I noticed that you had previously advised someone that sent in a sample solution of the error, so I was wondering waht the best course of action for diagnosing this is?
Back to top
Remco
#2 Posted : Tuesday, July 3, 2018 12:05:03 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
Hi, thanks for sharing this issue.

There's a broad range of things that can cause this error, for example:

- OutOfMemoryExceptions at run time
- StackOverflowExceptions in referenced code
- Unmanaged exceptions
- Accidental termination (i.e. Process.Kill)
- Hardware or platform instability
- NCrunch internal problem (rare these days, especially when working on proven frameworks and toolsets)

The hard part here is finding the source of the problem. Since the issue results in immediate termination of the process, there's no progress or error information to be retrieved.

Does your event viewer show you any information?

It might be possible to reproduce the issue with some consistency using Churn Mode. This may help with narrowing it down. If you can get one test that you know kicks the issue up, try running it under Churn Mode for an indefinite period of time to see if you can make it fail.
Back to top
samholder
#3 Posted : Wednesday, July 4, 2018 3:11:11 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 5/11/2012(UTC)
Posts: 94

Thanks: 28 times
Was thanked: 12 time(s) in 12 post(s)
it was indeed a StackOverflowException and it happened under some circumstances in the running of the app, which lead us to identifying it, and this fixed the tests

Thanks for the help
Back to top
1 user thanked samholder for this useful post.
Remco on 7/5/2018(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.044 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download