Build/Test Issues

NCrunch erroneously detecting project build failure

Started by kalebpederson on 6,411 views

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
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
You're right, the Processing Queue window contains more information:

[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
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

Post a reply

Log in to reply.