Build/Test Issues

NCrunch 4 - Instrumentation Mode - Optimized - System.IO.IOException

Started by CsabaF on 1,922 views

Hello,

I am getting these kind of errors using the new optimized instrumentation mode:

NCrunch: This project was built on server '(local)'
The file 'D:\[root folder]\Module\packages\NUnit.3.10.1\build\NUnit.props' could not be written to the workspace due to error: System.IO.IOException: More data is available.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost)
at nCrunch.Common.IO.FilePath.CopyTo(FilePath destinationPath, Boolean waitForLock)
at nCrunch.Core.ProjectItems.SnapshotComponentMember.WriteToFile(FilePath fileToWriteTo)
at nCrunch.Core.WorkspaceManagement.WorkspaceBuilder.(SnapshotComponentMember )

I have a large solution, with 150+ projects and about 10% of them fail with this issue.

I am running VS2017, the solution is targeting .NET 4.6.2 and obviously running NCrunch 4.0.

Thanks in advance!

Edited

Hi, thanks for sharing this issue.

Can you confirm whether this issue also appears when you use the legacy instrumentation mode? The problem looks like it is appearing long before the assembly is actually built (or instrumented).
No, it doesn't seem to happen with the legacy mode at all.
Thanks for confirming this. Does the issue appear with consistency? This one has me quite confused as the point of code throwing the error actually doesn't have anything to do with the new optimised mode at all. It must somehow be causing the issue indirectly.

Is there any chance you can isolate this issue with a code sample that you can share with me? You can submit small code samples through the NCrunch contact form.

Edited

Post a reply

Log in to reply.