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

Notification

Icon
Error

Testing Projects with Code Analysis enabled fail on Grid Node Server with Version 3.19.
GlobalConcepts
#1 Posted : Thursday, September 6, 2018 11:48:37 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 2/7/2013(UTC)
Posts: 52
Location: Germany

Thanks: 5 times
Was thanked: 6 time(s) in 6 post(s)
Related to some other issues we did an upgrade of our clients and our grid node server to version 3.19 yesterday evening.

Since that upgrade we receive the following error message while we try to run tests projects that have a reference on projects that have Code Analyses on Build enabled:

****************** BUILD OUTPUT FROM '<<Replaced Server Name>>' ******************

CA0001 : An unknown error occurred while running Code Analysis.

Disabling Code Analysis the tests will be executed fast and successful.
Would you please so kind to provide us steps to solve this problem?

Kind Regards
Sebastian
Remco
#2 Posted : Thursday, September 6, 2018 12:55:20 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi, thanks for sharing this issue.

Another user has also reported this problem. v3.19 contained some refactoring around the code analysis suppression that shouldn't have resulted in a functional change, but apparently in some environments it has. I haven't yet been able to reproduce this problem.

I'm wondering if you could try adding a Custom build property of 'RunCodeAnalysis' = 'False' on each of the projects involved. Can you confirm if this suppresses the issue?
GlobalConcepts
#3 Posted : Thursday, September 6, 2018 2:02:36 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 2/7/2013(UTC)
Posts: 52
Location: Germany

Thanks: 5 times
Was thanked: 6 time(s) in 6 post(s)
Thank you for your response!
Adding that Custom build property seems to work. Do we have to expect problems regarding "default" code analysis or is this just for ncrunch purposes?
Remco
#4 Posted : Thursday, September 6, 2018 11:14:58 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
This custom property only gets applied when NCrunch builds your project, so there's no risk of side effects here. The property is the same one that NCrunch is actually supposed to inject into your build anyway (since CodeAnalysis is off), but somehow this is misbehaving. We'll get to the bottom of it. For the time being, this should be an effective workaround.
GlobalConcepts
#5 Posted : Monday, September 10, 2018 7:14:19 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 2/7/2013(UTC)
Posts: 52
Location: Germany

Thanks: 5 times
Was thanked: 6 time(s) in 6 post(s)
solved with 3.20 :-)

Thanks for that!
1 user thanked GlobalConcepts for this useful post.
Remco on 9/10/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.031 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download