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

Notification

Icon
Error

NCrunch erroneously detecting project build failure
kalebpederson
#1 Posted : Wednesday, May 30, 2012 9:16:15 PM(UTC)
Rank: Member

Groups: Registered
Joined: 2/1/2012(UTC)
Posts: 25
Location: US

Thanks: 5 times
Was thanked: 3 time(s) in 3 post(s)
I have a VC++ project that I'm building with CLI/CLR support. It builds successfully but NC seems to think it failed. If I go to the directory where NCrunch placed everything I can see the output assembly and/or compile the project on the commandline successfully.

How can I debug this?

Thanks.

--Kaleb
Remco
#2 Posted : Thursday, May 31, 2012 4:37:11 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi Kaleb -

Right now VC++ isn't officially supported by NCrunch - there is still more testing and fixing to be performed before I feel confident saying that these projects will work without a hitch. However, there's a chance we can still get this to work for you. Most likely the error information is only available in the Processing Queue and not in the Tests Window (you may need to adjust your logging verbosity in your global configuration). If you like, I can also take a look at the log file if you can send through a bug report.


Cheers,

Remco
kalebpederson
#3 Posted : Thursday, May 31, 2012 3:02:55 PM(UTC)
Rank: Member

Groups: Registered
Joined: 2/1/2012(UTC)
Posts: 25
Location: US

Thanks: 5 times
Was thanked: 3 time(s) in 3 post(s)
You're right, the Processing Queue window contains more information:

Code:
[13:56:10.9226-BuildTask-50] ERROR (Compilation): My.Interop.Project:  (0): System.ArgumentException: Value does not fall within the expected range.
   at Mono.Cecil.ModuleWriter.WriteModuleTo(ModuleDefinition module, Stream stream, WriterParameters parameters)
   at Mono.Cecil.ModuleDefinition.Write(Stream stream, WriterParameters parameters)
   at Mono.Cecil.ModuleDefinition.Write(String fileName, WriterParameters parameters)
   at nCrunch.Compiler.StaticManipulation.BuiltAssembly.#=qfB_h8iDgveNRYQ$c0QXb4utc4Vg02$wojhTn8WLsCPw=.#=qjUD_hJ2J0Pc3JgOhZhwVRod8pUTV48WmNTbvqK1wPWM=()
   at nCrunch.Compiler.StaticManipulation.BuiltAssembly.#=q_r3LqUJZgZjPCWSYDr3_rA==(Action #=q18hUdGZMwDwhKyE0lBHoPg==)
   at nCrunch.Compiler.StaticManipulation.BuiltAssembly.Instrument(ComponentSourceLineMap sourceLineMap, IDictionary`2 codeFileIDsByFilePath, Boolean proxyProcessIsActive, Int32 componentId, IInstrumentationFilter[] instrumentationFilters)
   at nCrunch.Compiler.RemoteBuildRunner.#=qeftuZ3C2X20v96Jl0DjQaObBHnOGMTYrO1zkm1$$gc4=(ComponentBuildParameters #=qCKWIoiuPIRRzNxKV_YKpog==, String #=qfOXh39ORdamE9$M3rFfC1B8Yhg2yEb$l6VAv0iQ9Xaw=, BuildOutput #=qFKly1T4KWLczZrXbassfHQ==, String #=qUajCWehsM40yv2XjKk5ppFTV8DzLJpivuc0MWAXRpWY=)
   at nCrunch.Compiler.RemoteBuildRunner.Build(ComponentBuildParameters parameters)


Please let me know if that helps. If not I'll submit a bug report.

Thanks for NCrunch, it's wonderful!

--Kaleb
kalebpederson
#4 Posted : Thursday, May 31, 2012 3:17:37 PM(UTC)
Rank: Member

Groups: Registered
Joined: 2/1/2012(UTC)
Posts: 25
Location: US

Thanks: 5 times
Was thanked: 3 time(s) in 3 post(s)
After actually looking at the stack trace I decided to disable instrumentation for that project and now my solution builds, which is plenty good for now.

Thanks for the help.

--Kaleb
1 user thanked kalebpederson for this useful post.
Remco on 5/31/2012(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.049 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download