AV is still McAfee VirusScan Enterprise, which is continually updated.
I installed 2.8 (both the released version and the beta version you provided in this thread) as a test, and also have the problem there.
The problem however is a bit different than it was when I opened the thread. It very seldom gets into a simple loop. Instead, it starts "backtracking" in the assembly tree: After it has compiled some of the assemblies it suddenly reprocesses an earlier (parent) assembly, which invalidates all the children. Usually, after a couple of loops through this it gets done.
Build/Test Issues
NCrunch stuck in Processing/Reprocessing loop
Started by Daniel Rose on 28,125 views
I made a log, however there is no ComponentMemberUpdatedEvent: https://onedrive.live.com/redir?resid=1243F1CE2248975A%21103
Remco NCrunch Developer
#6582
06 Nov 2014 11:32 UTC
Thanks, the log was very insightful.
It looks like this is being caused by the scanner now targeting the assembly references inside the 'Program Files (x86)\Reference Assemblies' directory. NCrunch detects changes to referenced assemblies also, as this usually requires a rebuild. The handling for these dependencies is different to the normal source files, which is why they weren't included in the fix I provided earlier. The good news is that the logic is basically the same, so the same fix is also possible. The bad news is that I'll need to get you a new build in order to provide the fix, which may take a couple of weeks. I'll let you know as soon as I have something stable for you to try.
Cheers,
Remco
It looks like this is being caused by the scanner now targeting the assembly references inside the 'Program Files (x86)\Reference Assemblies' directory. NCrunch detects changes to referenced assemblies also, as this usually requires a rebuild. The handling for these dependencies is different to the normal source files, which is why they weren't included in the fix I provided earlier. The good news is that the logic is basically the same, so the same fix is also possible. The bad news is that I'll need to get you a new build in order to provide the fix, which may take a couple of weeks. I'll let you know as soon as I have something stable for you to try.
Cheers,
Remco
Post a reply
Log in to reply.