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

Notification

Icon
Error
Test fails without error message
Options
Previous Topic Next Topic
DanHil
#1 Posted : Monday, November 19, 2012 11:01:54 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
I have a test that fails without producing an error message.
The execution time always is exactly one second.
Doing a complete rebuild in VS showed that some files were in use. However NCrunch didn't report any build error.
Back to top
Remco
#2 Posted : Monday, November 19, 2012 7:59:45 PM(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)
This usually means the test runner has had an internal failure. Check the processing queue for the test task that failed - do you see an error message in the bottom pane?
Back to top
DanHil
#3 Posted : Monday, November 19, 2012 8:07:26 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
No, unfortunately, there was no error message. I checked.
Back to top
Remco
#4 Posted : Monday, November 19, 2012 8:21:35 PM(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)
Is it the same test that is failing consistently? Does it also fail if you run it directly via the UI (via clicking the 'run' option on the tests window)? Is there anything you would consider to be unique about the structure of this test?
Back to top
DanHil
#5 Posted : Monday, November 19, 2012 8:24:40 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
Yes, it was always the same test. Manually running it in the tests window didn't help.
Nothing about this test is unique, it is very ordinary and similar tests worked without problems.

The test now started working again - I think after I unlocked the files and did a rebuild all in VS and a reset in NCrunch.
Back to top
Remco
#6 Posted : Monday, November 19, 2012 8:34:14 PM(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)
Is the 'include static references in workspace' configuration setting disabled? Other than absolute file path references, this is the only way that it can be possible to have locking problems between VS and NCrunch. If you have this setting disabled for any of your projects, try turning it on - this may solve the problem.
Back to top
DanHil
#7 Posted : Tuesday, November 20, 2012 9:53:59 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
"Include static references in workspace" is True for all projects.
Absolute file references are not used.
I sent you a report, maybe it helps.
Back to top
Remco
#8 Posted : Tuesday, November 20, 2012 9:18:49 PM(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)
Is this the same solution that you've been experiencing intermittent xunit.dll build issues with?

The bug report shows NCrunch is failing to map the coverage data derived from the workspace, which suggests this may be a symptom of the same problem causing the xunit.dll build issue.
Back to top
DanHil
#9 Posted : Wednesday, November 21, 2012 12:22:00 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
It is the same solution, but the test is in a different project file.
I don't think it has anything to do with the xunit.dll issue. xunit.dll occurred very often, this problem occurred only as long as those files were locked. It didn't happen since.
Back to top
Remco
#10 Posted : Wednesday, November 21, 2012 7:02:24 PM(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)
Which files were they that you had locked and how were they locked?
Back to top
DanHil
#11 Posted : Wednesday, November 21, 2012 7:04:46 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
Project output files (DLL). They were locked because the program was still running.
Back to top
Remco
#12 Posted : Wednesday, November 21, 2012 10:00:20 PM(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)
There's a lot going on in this solution. I'm wondering if the fix you found in the other thread related to DLLs being referenced in the Bin\Debug directories may have also had an impact on this. Can you let me know if it happens again now that you've solved the other issue? I'm hoping that this problem is related and that we've seen the last of it - Mapping exceptions are almost impossible to analyse and inspect without clear steps to reproduce.
Back to top
DanHil
#13 Posted : Thursday, November 22, 2012 8:21:35 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
I couldn't reproduce it either. Maybe it was part of the problem with the references.
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 4.898 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download