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

Notification

Icon
Error
VS2012 update 2 seems to break NCrunch (on some systems)
Options
Previous Topic Next Topic
BKStrelioff
#1 Posted : Saturday, April 6, 2013 4:59:58 PM(UTC)
Rank: Member

Groups: Registered
Joined: 3/17/2012(UTC)
Posts: 23

Was thanked: 4 time(s) in 4 post(s)
I tried NCrunch 1.44, 1.45.11, and 1.45.12 with no real luck on one of my systems, but the other one seems to work okay.

What I see is the nCrunch.TestHost.x86.exe has stopped working,CheckOnline, Close, or Debug popup.

Problem signature:
Problem Event Name: APPCRASH
Application Name: nCrunch.TestHost.x86.exe
Application Version: 0.0.0.0
Application Timestamp: 50f47fbe
Fault Module Name: nCrunch.TestHost.x86.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 50f47fbe
Exception Code: 40000015
Exception Offset: 0000160d
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033
Additional Information 1: 79ed
Additional Information 2: 79edac7249921efddb8fda8eccf7598c
Additional Information 3: 68ee
Additional Information 4: 68eec54c4f91d9178ce9df9e4c209f52

Read our privacy statement online:
http://go.microsoft.com/...104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Back to top
 |  Edit by user
Remco
#2 Posted : Sunday, April 7, 2013 1:54:50 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 964 times
Was thanked: 1296 time(s) in 1202 post(s)
Thanks for reporting this. I'm wondering if I could ask a few quick questions to help narrow this down:

- Do you experience this problem with all solutions? Or just one in particular?
- How often does the crash occur? Does it happen on every test cycle?
- Do you notice the crash occurs several times in just one test cycle? Or only once?
- If you look in the Processing Queue window after the crash has occurred, can you see the test task that failed to run and the tests associated (they should all be marked with an artificial failure)?
- Does changing the 'Use hosted task runner' global configuration setting make any difference?

Thanks!

Remco
Back to top
BKStrelioff
#3 Posted : Sunday, April 7, 2013 10:47:11 PM(UTC)
Rank: Member

Groups: Registered
Joined: 3/17/2012(UTC)
Posts: 23

Was thanked: 4 time(s) in 4 post(s)
1) Just one solution (so far) on just one system (so far). Same solution works fine on other system(s)
2) Every time for all unit tests
3) It seems to happen on the first test in a cycle, and then blocks others. If I explicitly rerun any individual test, it seems to fail. It looks like during automatic testing 2 attempts are made to kick off tests per project, and both seem to fail the same way.
4) It appears that all tests are marked as failed.
5) Originally ran with "True", I changed to "False" and ... still fails in what appears to be the same pattern.
Back to top
Remco
#4 Posted : Sunday, April 7, 2013 11:25:37 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 964 times
Was thanked: 1296 time(s) in 1202 post(s)
Thanks for sharing these details. My suspicion is that this is being caused somehow by the code under test. If you set a breakpoint on the first line of code of one of your tests (i.e. the opening brace), then choose to debug the test, does it hit the breakpoint?

.. Or otherwise, are you making use of any facilities that will execute at the beginning of EVERY test in your codebase? For example, a SetUpFixture?
Back to top
BKStrelioff
#5 Posted : Sunday, April 7, 2013 11:52:46 PM(UTC)
Rank: Member

Groups: Registered
Joined: 3/17/2012(UTC)
Posts: 23

Was thanked: 4 time(s) in 4 post(s)
I am trying to verify that the code is the same on all systems -- there may be a difference in what TFS is downloading as "current". This seems to have left some lingering Fakes libraries/references on the problematic system.
Back to top
BKStrelioff
#6 Posted : Monday, April 8, 2013 2:51:34 PM(UTC)
Rank: Member

Groups: Registered
Joined: 3/17/2012(UTC)
Posts: 23

Was thanked: 4 time(s) in 4 post(s)
Okay, I zip'd and ship'd the working source tree from the "good" system to the "broken" system and things now work. So maybe I have something NCrunch related checked in (or missing) from TFS.

Regardless, I think this is a setup/config issue, and not a real NCrunch problem.
Back to top
1 user thanked BKStrelioff for this useful post.
Remco on 4/8/2013(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.039 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download