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

Notification

Icon
Error

NCrunch 4 - Instrumentation Mode - Optimized - System.IO.IOException
CsabaF
#1 Posted : Friday, November 8, 2019 10:29:14 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/14/2018(UTC)
Posts: 2
Location: Switzerland

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!
Remco
#2 Posted : Friday, November 8, 2019 11:51:53 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 5,830

Thanks: 754 times
Was thanked: 973 time(s) in 927 post(s)
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).
CsabaF
#3 Posted : Saturday, November 9, 2019 12:48:40 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/14/2018(UTC)
Posts: 2
Location: Switzerland

No, it doesn't seem to happen with the legacy mode at all.
Remco
#4 Posted : Saturday, November 9, 2019 10:23:04 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 5,830

Thanks: 754 times
Was thanked: 973 time(s) in 927 post(s)
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.
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.035 seconds.