The system cannot find the file specified - Build/Test Issues

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

Notification

Error

NCrunch Forum » General Support » Build/Test Issues » The system cannot find the file specified

2 Pages12 >

The system cannot find the file specified

Options

Previous Topic Next Topic

lprichar		#1 Posted : Thursday, February 13, 2014 4:23:53 AM(UTC)
Rank: Advanced Member Groups: Registered Joined: 7/12/2013(UTC) Posts: 41 Location: United States of America Thanks: 4 times		Dear NCrunch, I have a unit test that passes in MSTest, but fails in NCrunch. The line it fails on is: return await StorageFile.GetFileFromApplicationUriAsync("ms-appx:///Assets/SomeFile.pdf"); This is a Windows 8.1 project. When I get the result back in the unit test I am not awaiting, instead calling task.Wait(). I've tried turning off parallel execution, but no luck. Thank you so much for any assistance. Stack trace follows: System.AggregateException: One or more errors occurred. ---> System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002) at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() at MyProj.Windows8.Assets.AssetManager.<GetFile>d__0.MoveNext() in C:\Dev\MyProj.Windows8\MyProj.Windows8\Assets\AssetManager.cs:line 12#0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() at MyProj.Windows8.Assets.AssetManager.<GetForm482>d__4.MoveNext() in C:\Dev\MyProj.Windows8\MyProj.Windows8\Assets\AssetManager.cs:line 17#1 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() at MyProj.Windows8.ViewModels.Add482ViewModel.<GeneratePdfAsync>d__10.MoveNext() in C:\Dev\MyProj.Windows8\MyProj.Windows8\ViewModels\Add482ViewModel.cs:line 287#2 --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at System.Threading.Tasks.Task.Wait() at MyProj.Windows8.Test.ViewModels.Add482ViewModelTest.GeneratePdf_IsNotAlreadyGenerating482_SetsImagesToPrint() in C:\Dev\MyProj.Windows8\MyProj.Windows8.Test\ViewModels\Add482ViewModelTest.cs:line 23#3 ---> (Inner Exception #0) System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002) at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() at MyProj.Windows8.Assets.AssetManager.<GetFile>d__0.MoveNext() in C:\Dev\MyProj.Windows8\MyProj.Windows8\Assets\AssetManager.cs:line 12#4 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() at MyProj.Windows8.Assets.AssetManager.<GetForm482>d__4.MoveNext() in C:\Dev\MyProj.Windows8\MyProj.Windows8\Assets\AssetManager.cs:line 17#5 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult() at MyProj.Windows8.ViewModels.Add482ViewModel.<GeneratePdfAsync>d__10.MoveNext() in C:\Dev\MyProj.Windows8\MyProj.Windows8\ViewModels\Add482ViewModel.cs:line 287<---
Back to top

User Profile View All Posts by User View Thanks

Remco		#2 Posted : Thursday, February 13, 2014 10:37:04 AM(UTC)
Rank: NCrunch Developer Groups: Administrators Joined: 4/16/2011(UTC) Posts: 7,144 Thanks: 959 times Was thanked: 1290 time(s) in 1196 post(s)		Hi, thanks for sharing this issue. Looking at the stack trace, there seems to be a huge amount going on here. Is it possible that this issue is being caused by a resource file that NCrunch has not been made aware of? i.e. implicit file dependency. Can you cause the FileNotFoundException to occur outside all of the async code? It's very difficult to analyse the specific problem with so much other activity. Is there any chance you could build a working code sample that demonstrates the problem? If the problem is the async code itself, this would also be tremendously helpful. Cheers, Remco
Back to top

User Profile View All Posts by User View Thanks

lprichar		#3 Posted : Thursday, February 13, 2014 7:22:52 PM(UTC)
Rank: Advanced Member Groups: Registered Joined: 7/12/2013(UTC) Posts: 41 Location: United States of America Thanks: 4 times		I think the async stuff makes the stack trace look bigger. I could simplify if you like. Either way I don't believe it's an implicit file dependency problem because the file is included in VS (with a build action of Content). Does NCrunch support include files with a build action of Content? Incidentally I also tried adding the file in "Additional files to include", but it didn't help.
Back to top

User Profile View All Posts by User View Thanks

lprichar		#4 Posted : Thursday, February 13, 2014 9:08:01 PM(UTC)
Rank: Advanced Member Groups: Registered Joined: 7/12/2013(UTC) Posts: 41 Location: United States of America Thanks: 4 times		Hey Remco, I've duplicated this error in the "For Remco\NCrunchWin8Fail.sln" project that I've shared with you in the past on Dropbox. Hope that helps. Lee
Back to top

User Profile View All Posts by User View Thanks

Remco		#5 Posted : Friday, February 14, 2014 6:10:55 AM(UTC)
Rank: NCrunch Developer Groups: Administrators Joined: 4/16/2011(UTC) Posts: 7,144 Thanks: 959 times Was thanked: 1290 time(s) in 1196 post(s)		Hi Lee, Thanks for the code sample. This was really helpful in analysing the issue. You've managed to find a hole in NCrunch's Windows Store App support. When VSTest builds a test sandbox for a windows store test application, it copies the content files from all referenced projects into the sandbox. NCrunch hasn't been doing this, so the files haven't been in the sandbox and tests relying on them failed. I've put together a fix for this issue and prepared a build in case you'd like to give it a try. Download links are below: http://downloads.ncrunch.net/NCrunch_GridNodeServer_2.5.0.3.msi http://downloads.ncrunch.net/NCrunch_GridNodeServer_2.5.0.3.zip http://downloads.ncrunch.net/NCrunch_VS2008_2.5.0.3.msi http://downloads.ncrunch.net/NCrunch_VS2010_2.5.0.3.msi http://downloads.ncrunch.net/NCrunch_VS2010_2.5.0.3.zip http://downloads.ncrunch.net/NCrunch_VS2012_2.5.0.3.msi http://downloads.ncrunch.net/NCrunch_VS2012_2.5.0.3.zip http://downloads.ncrunch.net/NCrunch_VS2013_2.5.0.3.msi http://downloads.ncrunch.net/NCrunch_VS2013_2.5.0.3.zip I hope this does the trick. Thanks again, Remco
Back to top

User Profile View All Posts by User View Thanks

lprichar		#6 Posted : Friday, February 14, 2014 9:26:08 PM(UTC)
Rank: Advanced Member Groups: Registered Joined: 7/12/2013(UTC) Posts: 41 Location: United States of America Thanks: 4 times		I installed the VS2013 2.5.0.3 msi and now none of the tests in my main project work. They all return "NCrunch was unable to retrieve a meaningful result from this test due to an unexpected error - was the execution process terminated?". NCrunch can run successfully on my test project, so it must be something about my main project. I've submitted a bug report and hope that can give you something to work with. Please let me know if there is anything else I can do.
Back to top

User Profile View All Posts by User View Thanks

Remco		#7 Posted : Friday, February 14, 2014 11:35:11 PM(UTC)
Rank: NCrunch Developer Groups: Administrators Joined: 4/16/2011(UTC) Posts: 7,144 Thanks: 959 times Was thanked: 1290 time(s) in 1196 post(s)		Sorry Lee. The bug report you submitted contains the following error: System.Exception: Unable to launch Windows Store App Container. Return code -1 This is a wonderful error message that basically says that something went wrong while trying to launch the windows store test process. I'm wondering if you could check the Event Viewer to see if there is a more descriptive message there? Sometimes the app container can report things in there. My theory is that there may be some file or resource NCrunch is now copying to the sandbox that the app container doesn't like. If you like, I can make a speculative adjustment to the copy sequence to see if this helps, and issue you a new build in the hope that this will fix it. Otherwise, if you can update the sample project in a way that surfaces the problem, this would be really helpful in producing a reliable fix.
Back to top

User Profile View All Posts by User View Thanks

Remco		#9 Posted : Saturday, February 15, 2014 12:00:13 AM(UTC)
Rank: NCrunch Developer Groups: Administrators Joined: 4/16/2011(UTC) Posts: 7,144 Thanks: 959 times Was thanked: 1290 time(s) in 1196 post(s)		Hi Lee - This message here is pretty suspect: .NET Runtime version 4.0.30319.34011 - Loading profiler failed. COR_PROFILER is set to an invalid CLSID: 'NCover.ProfilerLauncher'. HRESULT: 0x800401f3. Process ID (decimal): 10184. Message ID: [0x2502]. Profilers such as NCover set an environment variable called 'COR_PROFILER' to a value that contains the CLSID of a COM object to handle profiler calls. If a profiler can't be found with this CLSID, the CLR will bug out in such a way. It's possible that this is a benign error that simply jumps up every time you load an application, and that it does nothing.. but it's still not a good thing. I find it interesting that this error is only showing for you under Windows Store Apps, and that it's started showing after you installed the fixed NCrunch build. Can you check your system's environment variables to make sure that no COR_PROFILER environment variable has been set globally on your machine? If you have NCover installed, it may also be worth temporarily removing it to see if this solves the problem.
Back to top		\| Edit by user

User Profile View All Posts by User View Thanks

lprichar		#10 Posted : Saturday, February 15, 2014 1:13:38 PM(UTC)
Rank: Advanced Member Groups: Registered Joined: 7/12/2013(UTC) Posts: 41 Location: United States of America Thanks: 4 times		There is a system variable called COR_PROFILER that is set to NCover.ProfilerLauncher. There are other system variables that mention NCover too. The odd thing is I don't have NCover installed (why would I when NCrunch is so awesome). Does NCrunch (or any other popular plugins like Resharper) use NCover under the covers?
Back to top

User Profile View All Posts by User View Thanks

Remco		#11 Posted : Sunday, February 16, 2014 10:31:54 PM(UTC)
Rank: NCrunch Developer Groups: Administrators Joined: 4/16/2011(UTC) Posts: 7,144 Thanks: 959 times Was thanked: 1290 time(s) in 1196 post(s)		It's difficult to rule out what other software may change on your machine, but I'm fairly certain that Jetbrains' products don't make use of NCover under the hood. NCrunch also doesn't touch it. I'd remove this environment variable as it's likely to create problems on your system. The COR_PROFILER value itself should normally be set to a CLSID (not a string constant), so I'm confused about why this has been set the way it is ... but anyway, does removing it solve the NCrunch app container issue?
Back to top

User Profile View All Posts by User View Thanks

lprichar		#12 Posted : Monday, February 17, 2014 4:02:55 AM(UTC)
Rank: Advanced Member Groups: Registered Joined: 7/12/2013(UTC) Posts: 41 Location: United States of America Thanks: 4 times		I removed COR_PROFILER and in the event logs got: .NET Runtime version 4.0.30319.34011 - Loading profiler failed. COR_ENABLE_PROFILING was set properly, but COR_PROFILER was not. COR_PROFILER must be set to the CLSID of the profiler to load. Process ID (decimal): 9264. Message ID: [0x2500]. So I removed COR_ENABLE_PROFILING and that left me with the errors I've already shown. I tried commenting out every one of my tests and mocks in the Win 8.1 Unit Test project and then adding in just a single test that just asserted 1 was equal to 1 and the unit test still failed (NCrunch was unable to retrieve a meaningful result from this test due to an unexpected error - was the execution process terminated?). I tried completely uninstalling NCrunch 2.5.0.3 and then installing it again, and no difference. I tried removing the reference to every one of the projects (including PCL's) in my project. Once I removed the reference to the Windows 8.1 Store App then it was able to run my test. So something in my main project that is unrelated to my unit tests is causing NCrunch 2.5.0.3 (but not 2.4) to fail. I guess I could start commenting out all of my classes one by one, but that is a non-trivial exercise that I'd rather not go down, at least not yet. Any other thoughts?
Back to top

User Profile View All Posts by User View Thanks

Remco		#13 Posted : Monday, February 17, 2014 7:37:16 AM(UTC)
Rank: NCrunch Developer Groups: Administrators Joined: 4/16/2011(UTC) Posts: 7,144 Thanks: 959 times Was thanked: 1290 time(s) in 1196 post(s)		Ok - that confirms that the COR_PROFILER issue is benign. Good that you've cleaned it up, but I guess it hasn't solved the app container issue, so something else is amiss. The change in the 2.5.0.3 build basically just copies content files from the projects being referenced by your test project. My theory is that one of these content files somehow disagrees with the app container, and it bugs out with a fairly typical app container error (i.e. something extremely obscure). I have some ideas for changes I might be able to make to the build to sort this out, but they're all highly speculative and likely would end up wasting your time. Is there any chance you can get me another test solution that can surface the issue?
Back to top		\| Edit by user

User Profile View All Posts by User View Thanks

lprichar		#14 Posted : Monday, February 17, 2014 12:52:49 PM(UTC)
Rank: Advanced Member Groups: Registered Joined: 7/12/2013(UTC) Posts: 41 Location: United States of America Thanks: 4 times		I can only get you another test solution if I knew what the problem was. As I mentioned to find out what the problem is I would need to comment out most of the code in my main project with a binary search until I found the file or files that were failing. That would be extremely time consuming. There's also the option of sharing the code of our main code base, but I assure you my employer would not be happy with that. Could you get me a build that has more thorough logging? For instance every time you copy a file put in a log.Debug of what was copied? Then maybe we could discover which file it was that was failing?
Back to top

User Profile View All Posts by User View Thanks

Remco		#15 Posted : Monday, February 17, 2014 11:01:50 PM(UTC)
Rank: NCrunch Developer Groups: Administrators Joined: 4/16/2011(UTC) Posts: 7,144 Thanks: 959 times Was thanked: 1290 time(s) in 1196 post(s)		I can only wish it was that simple :( Windows' handling of Store Apps is essentially a black box. The only way to initialise them from user code is through a little known and poorly documented API that spawns the process outside the usual Win32 methods, with very stringent security constraints and no opportunity for user code what-so-ever. When the creation of the process fails, there is usually no clear error information and the only way to troubleshoot is through logical deduction and blind guessing. Windows Store Apps were clearly not designed to be run within a test sandbox. Visual Studio makes use of a considerable amount of magic to make this happen, and emulating this behaviour in NCrunch was an expensive and challenging exercise. Because of this, trying to troubleshoot such a problem without a way to reproduce it is nearly impossible. I could try sending builds with speculative fixes to attempt to narrow things down, but with no way to target code that will give me more information about the problem, there'll probably be many many builds and I think we'll both go mad. I'd be happy to deal with your employer if there are conditions under which they will let me access the source code (i.e. NDA etc). Let me know if this is of interest to you.
Back to top

User Profile View All Posts by User View Thanks

Remco		#16 Posted : Monday, February 17, 2014 11:05:14 PM(UTC)
Rank: NCrunch Developer Groups: Administrators Joined: 4/16/2011(UTC) Posts: 7,144 Thanks: 959 times Was thanked: 1290 time(s) in 1196 post(s)		One thought just occurred to me that might help in narrowing this down quickly. The 2.5.0.3 change involved just the copying of content files. These are files marked with the <Content> tag inside the project XML files. I'm not sure how many projects you have in the space of your application, but changing the <Content> tags to <None> tags would in theory disable the copying for each of the files one at a time. You could do it with a find and replace across the project files, then selectively switch them back on until the problem appears. I'm not sure if this approach is ideal for you but I thought I would suggest it.
Back to top

User Profile View All Posts by User View Thanks

lprichar		#17 Posted : Tuesday, February 18, 2014 2:26:50 AM(UTC)
Rank: Advanced Member Groups: Registered Joined: 7/12/2013(UTC) Posts: 41 Location: United States of America Thanks: 4 times		Good idea, no luck. I tried creating a bran new unit test project with only a single test in it to rule out anything specific to my existing unit test project. It passed. Then I references my main project. It failed. Then I edited the .csproj for the main project to replace all <Content> tags with <None> tags. It still failed. I guess it's unrelated to included content? You sure nothing else relevant changed between 2.4 and 2.5.0.3? Perhaps I should try 2.5.0.2? I'm afraid the binary search is the only thing left in my repertoire. I'll also talk to my customer, although it will be a hard sell, and likely won't help my cause of convincing them to buy a copy for everyone on the team :).
Back to top

User Profile View All Posts by User View Thanks

Remco		#18 Posted : Tuesday, February 18, 2014 3:15:44 AM(UTC)
Rank: NCrunch Developer Groups: Administrators Joined: 4/16/2011(UTC) Posts: 7,144 Thanks: 959 times Was thanked: 1290 time(s) in 1196 post(s)		The copying of content files takes into account the project dependency tree, which means that if your main project depends on any other projects that contain content files, then these contents files will also be copied. Does your main project depend on any other projects in your solution? Perhaps one option could be to try setting your sample test project to point at different projects in your solution .. maybe this will help with narrowing down the issue. I've been digging in my brain for a way we can analyse this issue, and I'm wondering if you might be interested in trying a new build. The 2.5.0.6 build below contains several changes that I think will help us here: 1. This build will now report the files copied in its trace information. If you turn on the 'Log to output window' global configuration option, and set the 'Log verbosity' to 'Medium', watch out for the messages saying: Copying content file X to windows store sandbox at Y. This won't tell us which files may be messing up the sandbox, but it can provide extra information that could prove useful. These details will also be included in any bug report you send to me from this build. 2. You can now entirely disable the copying of content files by setting an environment variable on your machine. If you set 'NCrunch.NoContentCopying' equal to '1', NCrunch will avoid copying the content files. It's a bit of a hack, but should help us with confirming whether there was another change in 2.5 that has caused a problem. If you try this and the build still doesn't work, also keep an eye out in the log file just to make sure the files aren't being copied and the environment variable has had the intended effect. 3. I've adjusted the sequence of file copying into the sandbox to reduce the risk of clashing between the projects. Although I haven't isolated any situations where the previous method would create a problem, the Windows Store sandbox contains many surprises and the new approach is likely to be safer anyway. Something that may also be worth trying is comparing NCrunch's Windows Store App sandbox with the one usually created by VS/MSTest. If you right click on the failing test in the Tests Window, then choose Advanced->Browse To Workspace, look for the NCrunchAppx directory underneath the project's build outputs. This directory should be fairly similar to the Appx directory created by VS/MSTest when they run your tests normally. There'll likely be a few obvious differences (such as NCrunch DLLs instead of the VS ones and references to these in the package manifest), but the rest of the contents should be more or less the same. Do you notice any big differences that look out of place? Particularly around content files or package manifests? http://downloads.ncrunch.net/NCrunch_GridNodeServer_2.5.0.6.msi http://downloads.ncrunch.net/NCrunch_GridNodeServer_2.5.0.6.zip http://downloads.ncrunch.net/NCrunch_VS2008_2.5.0.6.msi http://downloads.ncrunch.net/NCrunch_VS2010_2.5.0.6.msi http://downloads.ncrunch.net/NCrunch_VS2010_2.5.0.6.zip http://downloads.ncrunch.net/NCrunch_VS2012_2.5.0.6.msi http://downloads.ncrunch.net/NCrunch_VS2012_2.5.0.6.zip http://downloads.ncrunch.net/NCrunch_VS2013_2.5.0.6.msi http://downloads.ncrunch.net/NCrunch_VS2013_2.5.0.6.zip
Back to top

User Profile View All Posts by User View Thanks

lprichar		#19 Posted : Wednesday, February 19, 2014 3:28:46 AM(UTC)
Rank: Advanced Member Groups: Registered Joined: 7/12/2013(UTC) Posts: 41 Location: United States of America Thanks: 4 times		Ok, finally got around to a binary search through the project. The file that is failing is App.xaml. The line of code that is failing is <locators:ViewModelLocator x:Key="Locator" />. That should define a variable that will be available to all xaml pages throughout the app, and it does work in MSTest yet fail in nCrunch. I've updated the sample in Dropbox so you can see it in action. Any idea why? p.s. I haven't yet tried 2.5.0.6 or any of your suggestions in the last post, but I still can if that would help.
Back to top

User Profile View All Posts by User View Thanks

Remco		#20 Posted : Wednesday, February 19, 2014 6:16:07 AM(UTC)
Rank: NCrunch Developer Groups: Administrators Joined: 4/16/2011(UTC) Posts: 7,144 Thanks: 959 times Was thanked: 1290 time(s) in 1196 post(s)		Thanks for the analysis! I've managed to reproduce and resolve the issue. A new build is available if you'd like to try it: http://downloads.ncrunch.net/NCrunch_GridNodeServer_2.5.0.7.msi http://downloads.ncrunch.net/NCrunch_GridNodeServer_2.5.0.7.zip http://downloads.ncrunch.net/NCrunch_VS2008_2.5.0.7.msi http://downloads.ncrunch.net/NCrunch_VS2010_2.5.0.7.msi http://downloads.ncrunch.net/NCrunch_VS2010_2.5.0.7.zip http://downloads.ncrunch.net/NCrunch_VS2012_2.5.0.7.msi http://downloads.ncrunch.net/NCrunch_VS2012_2.5.0.7.zip http://downloads.ncrunch.net/NCrunch_VS2013_2.5.0.7.msi http://downloads.ncrunch.net/NCrunch_VS2013_2.5.0.7.zip The problem seemed to be caused by the existence of .xaml files in the sandbox directory. It's a bit of a mystery to me why this would cause the container to explode, but such behaviour is not atypical of the windows store environment.
Back to top
1 user thanked Remco for this useful post.		lprichar on 2/19/2014(UTC)
User Profile View All Posts by User View Thanks

Users browsing this topic
Guest

2 Pages12 >

NCrunch Forum » General Support » Build/Test Issues » The system cannot find the file specified

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.