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

Notification

Icon
Error
3 Pages123>
Projects won't build
Options
Previous Topic Next Topic
DanHil
#1 Posted : Monday, November 12, 2012 12:56:27 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
I have two unit test projects that won't build right now.

The first built fine just a few minutes ago. Building it with Visual Studio completes successfully, so there are no "real" errors preventing the build.
The problem is, I can't say what is preventing the build, because I get no error message from NCrunch.
And now, after a few more minutes, it starts building successfully again.
In another solution I have a prject that just won't build ever - also without any message as to why.
I noticed this already several times. I can't provide repro or any other details, though. I thought I report it anyway.

The second problem might be easier to solve:
The unit test is using xUnit 1.9.1.
I get the following error message:
Quote:
An error occurred while analysing this project after it was built: Gallio.Model.ModelException: An exception occurred while invoking a test driver. ---> System.IO.FileLoadException: Could not load file or assembly 'xunit, Version=1.9.0.1566, Culture=neutral, PublicKeyToken=8d05b1bb7a6fdb6c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly 'xunit, Version=1.9.0.1566, Culture=neutral, PublicKeyToken=8d05b1bb7a6fdb6c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly 'file:///C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2010\Xunit\Latest\xunit.dll' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
at System.Reflection.Assembly.LoadFrom(String assemblyFile)
at nCrunch.Common.CustomAssemblyResolver.ResolveAssemblyWithShortName(String shortAssemblyName)
at nCrunch.Common.CustomAssemblyResolver.#=q5ZOMBoFn6JhzVvKsyjM6qebvz8XPGlMEQvgZewjf_GA=(Object #=qK3fBvt9GdPN$FAzPGO_Uuw==, ResolveEventArgs #=q_MaGRC82tujm7oDSmrc2Og==)
at System.AppDomain.OnAssemblyResolveEvent(RuntimeAssembly assembly, String assemblyFullName)
--- End of inner exception stack trace ---
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
at System.Reflection.Assembly.LoadFrom(String assemblyFile)
at nCrunch.Common.CustomAssemblyResolver.ResolveAssemblyWithShortName(String shortAssemblyName)
at nCrunch.Common.CustomAssemblyResolver.#=q5ZOMBoFn6JhzVvKsyjM6qebvz8XPGlMEQvgZewjf_GA=(Object #=qK3fBvt9GdPN$FAzPGO_Uuw==, ResolveEventArgs #=q_MaGRC82tujm7oDSmrc2Og==)
at System.AppDomain.OnAssemblyResolveEvent(RuntimeAssembly assembly, String assemblyFullName)
--- End of inner exception stack trace ---
at Gallio.XunitAdapter.Model.XunitTestExplorer.TryGetTypeTest(ITypeInfo type, Test assemblyTest)
at Gallio.XunitAdapter.Model.XunitTestExplorer.GetAssemblyTest(IAssemblyInfo assembly, Test parentTest, Version frameworkVersion, Boolean populateRecursively)
at Gallio.XunitAdapter.Model.XunitTestExplorer.ExploreImpl(IReflectionPolicy reflectionPolicy, ICodeElementInfo codeElement)
at Gallio.Model.Helpers.TestExplorer.Explore(IReflectionPolicy reflectionPolicy, ICodeElementInfo codeElement)
at Gallio.Model.Helpers.SimpleTestDriver.GenerateTestModel(IReflectionPolicy reflectionPolicy, IEnumerable`1 codeElements, IMessageSink messageSink)
at Gallio.Model.Helpers.SimpleTestDriver.DescribeImpl(IReflectionPolicy reflectionPolicy, IList`1 codeElements, TestExplorationOptions testExplorationOptions, IMessageSink messageSink, IProgressMonitor progressMonitor)
at Gallio.Model.BaseTestDriver.Describe(IReflectionPolicy reflectionPolicy, IList`1 codeElements, TestExplorationOptions testExplorationOptions, IMessageSink messageSink, IProgressMonitor progressMonitor)
at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.<>c__DisplayClass17.<DescribeImpl>b__15(ITestDriver driver, IList`1 items, Int32 driverCount)
at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.ForEachDriver[T](MultiMap`2 testFrameworkPartitions, Func`4 func)
--- End of inner exception stack trace ---
at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.ForEachDriver[T](MultiMap`2 testFrameworkPartitions, Func`4 func)
at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.DescribeImpl(IReflectionPolicy reflectionPolicy, IList`1 codeElements, TestExplorationOptions testExplorationOptions, IMessageSink messageSink, IProgressMonitor progressMonitor)
at Gallio.Model.BaseTestDriver.Describe(IReflectionPolicy reflectionPolicy, IList`1 codeElements, TestExplorationOptions testExplorationOptions, IMessageSink messageSink, IProgressMonitor progressMonitor)
at nCrunch.TestExecution.Frameworks.Gallio.GallioWrapper.FindFrameworkTestsInAssembly(ReflectedAssembly assembly, String assemblyFilePath, String[] referencedAssemblyFilePaths)
at nCrunch.TestExecution.Frameworks.Gallio.GallioTestFramework.FindFrameworkTestsInAssembly(ReflectedAssembly assembly, String assemblyFilePath, String[] referencedAssemblyFilePaths)
at nCrunch.TestExecution.TestFinder.FindTestsForFrameworks(ReflectedAssembly assembly, String assemblyFilePath, String[] referencedAssemblyFilePaths, TestFrameworkDescription[] frameworks)
at nCrunch.TestExecution.RemoteTaskRunner.AnalyseAssembly(TestFrameworkDescription[] applicableFrameworks)


I already replaced the xUnit version in c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2010\Xunit\Latest\ with the version my test project is using.
That solved a similar problem for a second unit test project. That second project is now building and crunching fine - using the same version of xUnit as the project this error message is from.

Any ideas?

I am currently evaluating NCrunch and while I really like the idea and how it works, I find it a bit hard to use, because of the many strange and hardly understandable errors I get.
Back to top
 |  Edit by user
DanHil
#2 Posted : Monday, November 12, 2012 1:44:29 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
I was able to fix the exception by updating the version number in c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2010\Xunit\Latest\Gallio.XunitAdapterLatest.gallioplugin
Back to top
Remco
#3 Posted : Monday, November 12, 2012 8:09:48 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)
Hi Dan,

Thanks for sharing these issues and for your feedback. The symptoms you've described (with the lack of error reporting) are consistent with an internal problem of some kind. These sorts of issues are becoming rarer and I endeavour to resolve them where ever they can be identified, as they are extremely confusing and not helpful at all.

Nice work in resolving the xUnit compatibility issue. I'll make sure to include this in the next version of NCrunch so that the problem will not present itself for others.

I have a feeling that this may have been related to the internal problem that caused the engine to stall, but if not, you can usually get more information about the stalled build by having a look at the task in the processing queue. The processing queue presents a more physical view of internal failures than the Tests Window and it may be able to provide you with a meaningful error message. You do also have the option to submit a bug report, in which case I'll have a look at the issue on your behalf and advice you of a workaround or supply a fix.


Thanks!

Remco
Back to top
DanHil
#4 Posted : Tuesday, November 13, 2012 8:31:58 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
Indeed, the processing queue is more helpful. For the project that simply refuses to build, I get this:

Quote:
[09:25:23.1056-BuildTask-8] ERROR (Compilation): Hyprlinkr.UnitTest: (0): Gallio.Model.ModelException: An exception occurred while invoking a test driver. ---> System.IO.FileNotFoundException: Could not load file or assembly 'xunit, Version=1.9.0.1566, Culture=neutral, PublicKeyToken=8d05b1bb7a6fdb6c' or one of its dependencies. Das System kann die angegebene Datei nicht finden.
at Gallio.XunitAdapter.Model.XunitTestExplorer.TryGetTypeTest(ITypeInfo type, Test assemblyTest)
at Gallio.XunitAdapter.Model.XunitTestExplorer.GetAssemblyTest(IAssemblyInfo assembly, Test parentTest, Version frameworkVersion, Boolean populateRecursively)
at Gallio.XunitAdapter.Model.XunitTestExplorer.ExploreImpl(IReflectionPolicy reflectionPolicy, ICodeElementInfo codeElement)
at Gallio.Model.Helpers.TestExplorer.Explore(IReflectionPolicy reflectionPolicy, ICodeElementInfo codeElement)
at Gallio.Model.Helpers.SimpleTestDriver.GenerateTestModel(IReflectionPolicy reflectionPolicy, IEnumerable`1 codeElements, IMessageSink messageSink)
at Gallio.Model.Helpers.SimpleTestDriver.DescribeImpl(IReflectionPolicy reflectionPolicy, IList`1 codeElements, TestExplorationOptions testExplorationOptions, IMessageSink messageSink, IProgressMonitor progressMonitor)
at Gallio.Model.BaseTestDriver.Describe(IReflectionPolicy reflectionPolicy, IList`1 codeElements, TestExplorationOptions testExplorationOptions, IMessageSink messageSink, IProgressMonitor progressMonitor)
at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.<>c__DisplayClass17.<DescribeImpl>b__15(ITestDriver driver, IList`1 items, Int32 driverCount)
at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.ForEachDriver[T](MultiMap`2 testFrameworkPartitions, Func`4 func)
--- End of inner exception stack trace ---
at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.ForEachDriver[T](MultiMap`2 testFrameworkPartitions, Func`4 func)
at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.DescribeImpl(IReflectionPolicy reflectionPolicy, IList`1 codeElements, TestExplorationOptions testExplorationOptions, IMessageSink messageSink, IProgressMonitor progressMonitor)
at Gallio.Model.BaseTestDriver.Describe(IReflectionPolicy reflectionPolicy, IList`1 codeElements, TestExplorationOptions testExplorationOptions, IMessageSink messageSink, IProgressMonitor progressMonitor)
at nCrunch.TestExecution.Frameworks.Gallio.GallioWrapper.FindFrameworkTestsInAssembly(ReflectedAssembly assembly, String assemblyFilePath, String[] referencedAssemblyFilePaths)
at nCrunch.TestExecution.Frameworks.Gallio.GallioTestFramework.FindFrameworkTestsInAssembly(ReflectedAssembly assembly, String assemblyFilePath, String[] referencedAssemblyFilePaths)
at nCrunch.TestExecution.TestFinder.FindTestsForFrameworks(ReflectedAssembly assembly, String assemblyFilePath, String[] referencedAssemblyFilePaths, TestFrameworkDescription[] frameworks)
at nCrunch.Compiler.StaticManipulation.BuiltAssembly.DiscoverTests(TestFrameworkDescription[] applicableTestFrameworks)
at nCrunch.Compiler.RemoteBuildRunner.#=qPVZ1Qvt7K1dg$S2Tsbki14jXz55V81a4b0lw2Gy2H9I=(ComponentBuildParameters #=qaLbij$nvLcp1xzKxt0ECzQ==, String #=q3Qo9mUTR8Ej_efd8kOmuaRPOgcadukhysqWjzfCknIs=, BuildOutput #=qc1a02FFghipoiqbEEWdEuA==, String #=qib4s6fOXht5wNWFzsTveI52_75PbtixMjh7DSUYzHhg=)
at nCrunch.Compiler.RemoteBuildRunner.Build(ComponentBuildParameters parameters)


Please note: This is the same machine. I have no idea where it still gets that version number from.
I re-started Visual Studio after changing the version number in the gallioplugin file and searching in files for 1566 in the NCrunch directory returns no files.
The unit test itself references version 1.9.1.1600
Back to top
 |  Edit by user
Remco
#5 Posted : Tuesday, November 13, 2012 9:26:50 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 Dan,

Try replacing the xunit.dll file inside your NCrunch installation directory (under Xunit\Latest). I have a feeling this is caused by a version inconsistency with the Xunit used by your solution and specified in the gallioplugin file. NCrunch uses binding redirections to force the test runner to use its own Xunit version.

Something I don't quite understand is why the binding redirections have initially failed in your situation. Normally, NCrunch should just redirect you to its own version of Xunit and all should work without problems. Are you making use of any other frameworks that tie in with Xunit? Or is there anything in the 1.9.1 release of Xunit that your code specifically relies on?


Cheers,

Remco
Back to top
 |  Edit by user
DanHil
#6 Posted : Tuesday, November 13, 2012 1:35:13 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
Quote:
Try replacing the xunit.dll file inside your NCrunch installation directory (under Xunit\Latest)


That's what I already did, see first and second post.

Before I replaced it I got error messages that the version used in my unit test could not be found.
My unit test uses the xUnit.net Extensions nuget package which depends on xunit 1.9.1 (exact). That would explain the initial error I got before replacing the xunit.dll that came with NCrunch.

I just found out that changing "Framework utilisation type for Gallio/XUnit" from "UseStaticAnalysis" to "UseDynamicAnalysis" makes the error about not finding version 1.9.0.1566 go away.

BTW: One of my projects just failed out of the blue with this message:

..\..\..\..\..\..\..\..\windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (2868)#0: Unable to copy file "obj\Debug\GA.CoreData.UnitTests.dll" to "bin\Debug\GA.CoreData.UnitTests.dll". The process cannot access the file 'bin\Debug\GA.CoreData.UnitTests.dll' because it is being used by another process.

The processing queue says the same:
[14:27:49.4405-BuildTask-85] ERROR (Compilation): GA.CoreData.UnitTests: C:\windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (2868): Unable to copy file "obj\Debug\GA.CoreData.UnitTests.dll" to "bin\Debug\GA.CoreData.UnitTests.dll". The process cannot access the file 'bin\Debug\GA.CoreData.UnitTests.dll' because it is being used by another process.

I was rather quickly doing changes with "Save All" inbetween. Shortly before it stopped working, many of my tests were marked as failed because there was no result - I think NCrunch somehow crashed or something. The message was "NCrunch was unable to retrieve a meaningful result from this test due to an unexpected error - was the execution process terminated?"
Back to top
 |  Edit by user
Remco
#7 Posted : Tuesday, November 13, 2012 9:44:03 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)
Hi Dan,

Is there any chance you could file a bug report after you receive the resolution problem with the framework utilisation type set to 'UseStaticAnalysis'? I'd really like to take a look at the log file to find out why the resolution logic is going askew here.

I'm wondering if I can ask you some questions about the next problem you've just experienced (around file copying) to see if I can help work out what is going wrong here:

- Does this problem happen consistently? Intermittently? Infrequently?
- Do you have any customisations in your build process? i.e. special build steps or hand-coded changes to project files
- Do you have any integration tests that contain absolute file path references (i.e non-relative paths)?
- Do you have any integration tests that spawn additional processes during their execution?

If the problem happens again, it would also be great if you could submit a bug report straight afterwards. The more information we can get about this problem, the faster we can solve it.


Thanks!

Remco
Back to top
DanHil
#8 Posted : Wednesday, November 14, 2012 9:21:11 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
About the issue with static analysis: Please find it here: http://rapidshare.com/files/3445201435/Report.zip

About file copying:

  1. It happened twice since I started using NCrunch a few days ago. I don't see any pattern so far.
  2. There are no custom build steps
  3. No
  4. No, not that I am aware of.
Back to top
Remco
#9 Posted : Wednesday, November 14, 2012 10:05:45 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 bug report. I'm looking into the static analysis issue right now .. though I haven't had any luck in reproducing it yet. I suspect this might be something related to your machine instead of the solution you're working in.

If you manage to catch the engine after it fails again, it would be great if you could capture a bug report. This would be very helpful in reproducing this issue also.

Thanks!

Remco
Back to top
DanHil
#10 Posted : Wednesday, November 14, 2012 10:28:27 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
I will try to reproduce the issue with the static analysis later today on a different machine. If I can reproduce it, you should be able to reproduce it too, as I am testing it with an open-source project: https://github.com/ploeh/Hyprlinkr
Back to top
DanHil
#11 Posted : Wednesday, November 14, 2012 4:12:57 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
I uploaded a bug report regarding the File In Use problem: https://rapidshare.com/f...76/Report_FileInUse.zip

Before that error occurred NCrunch was showing errors in the unit tests that already had been fixed. They didn't disappear when I right clicked the project and chose "Rebuild selected component".
Back to top
Remco
#12 Posted : Wednesday, November 14, 2012 8:18:15 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)
Thanks for this! I'm taking a look at this issue now.

It looks as though the engine has managed to work itself into an invalid state. I've noticed the following exception being thrown before this, and I'm wondering if it may have something to do with the issues appearing later down the line:

System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\daniel.hilgarth\AppData\Local\NCrunch\9444\21\GA.CoreData.IntegrationTests\DisposeTestDataAttribute.cs'

.. This happens when NCrunch is trying to build/update one of its workspaces to contain the latest version of your code.

Is there anything within your build or test code that manipulates source files in any way?

Thanks also for supplying the link to the open source project. I've inspected this and it seems to work normally on my machine (without upgrading NCrunch's Xunit), I'm keen to hear if there's any difference in behaviour for the other computer you try it on.

Thanks again for all your help. I've noticed you've been having issues with bug reporter connectivity - if you find it easier, you can also submit bug reports using the contact form on this website.

Cheers,

Remco
Back to top
DanHil
#13 Posted : Wednesday, November 14, 2012 8:57:48 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
There is nothing in my build that changes source files.
I manually renamed that file.
It was first named DisposeTestDataAttribute.cs and I renamed it to DisposeAutoTestDataAttribute.cs.
And that rename was what I meant, when I said "Before that error occurred NCrunch was showing errors in the unit tests that already had been fixed".
Unit tests that used the class DisposeAutoTestDataAttribute were failing with the error that DisposeTestDataAttribute could not be found, although I already had changed all occurrences of that class to the new name.

About Hyprlinkr: I can't get it to fail on the other machine either. I am going to simply restart the offending machine tomorrow and see what happens.

Thanks for the hint with the contact form :-) I am behind a corporate proxy all day long and the bug reporter doesn't want to play with it.
Back to top
Remco
#14 Posted : Thursday, November 15, 2012 5:26:35 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)
Interesting.. When renaming the DisposeTestDataAttribute file, did you do so inside the NCrunch workspace? Or in your foreground solution?
Back to top
DanHil
#15 Posted : Thursday, November 15, 2012 6:30:58 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
Naturally in the "foreground" solution AKA Visual Studio.
I am not sure which of the two following approaches I used:

1. (More likely)
a. Put cursor on class name
b. Hit Ctrl R + R to bring up ReSharpers Rename refactor dialog
c. Entered the new name
d. File gets automatically renamed along with the class

2. (Less likely)
a. Change class name in VS Text editor
b. Hit Ctrl + Shift + Alt + F10 to bring up the menu for the little bar under the renamed class
c. Choose the Rename class refactoring of VS
d. Alt + Enter on the renamed class to bring up ReSharpers Action menu
c. Choose Rename file to match class name
Back to top
Remco
#16 Posted : Thursday, November 15, 2012 7:38:47 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 problem seems consistent with a workspace synchronisation problem ... which is something that did show up in early versions of NCrunch, but hasn't been reported for quite some time. This makes me a little anxious as I was hoping to have seen the last of these sorts of issues (they are very hard to reproduce and fix).

The basic workaround when you see this happen is to just hit the 'reset' button on the tests window, or Enable/Disable NCrunch to flush out and rebuild the workspaces. If you manage to establish some clear steps to reproduce, I'd really like to take a closer look .. but until then, we may just be chasing ghosts with this one :(
Back to top
DanHil
#17 Posted : Thursday, November 15, 2012 7:48:26 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
I understand. I am sorry but I can't offer reproduction steps currently.
Back to top
DanHil
#18 Posted : Thursday, November 15, 2012 8:01:20 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
Remco, I am sorry to say that, but I have another one.

One of the unit test projects refuses to build. I had this yesterday already several times.
I get the following error in the processing queue:
Quote:

[08:53:59.8725-BuildTask-131] ERROR (Internal): System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\daniel.hilgarth\AppData\Local\NCrunch\9812\64\_ncrunchreferences\xunit.dll'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at Mono.Cecil.ModuleDefinition.GetFileStream(String fileName, FileMode mode, FileAccess access, FileShare share)
at Mono.Cecil.ModuleDefinition.ReadModule(String fileName, ReaderParameters parameters)
at nCrunch.Core.BuildManagement.AssemblyVersionReader.ReadAssemblyVersion(String assemblyFilePath)
at nCrunch.Core.BuildManagement.ReferencedAssemblySet.#=qiuSNEpitBV95sFr3OdZ_44Wg6Bj8SPaipBEqYu2dsaEYapslEBHq6sLXBWm0hPb1moLB6doMSS4Qs2EiSK__zg==(BuildAssemblyReference #=q0BRqR7s74HYjuyLqomA7IK4Q4$zCU9lp9h5BNJ4SUFs=)
at nCrunch.Core.BuildManagement.ReferencedAssemblySet.#=qeN0J_Wh_NpM0eOstHg7BkYnO1WJVEkzLjE6i_wCM4FhXbadv66PBoL0nm5NL1GFC(IEnumerable`1 #=q9I5dFwllCs6sd2cU$wFhv3ujf42JO3o8Ilqxb8smXUM=, TestFrameworkFileReference #=qbLQJZxOWA2EKx8FDXueWuXpnj9O9ywA2EduLatlGOOA=)
at nCrunch.Core.BuildManagement.ReferencedAssemblySet.#=qnenp7Oj2SlbxvaU_7STDPJwCJCKHlSK1OQET7IZ$jEtBVQ7gf5q8cIvVkDDuo4Fx39R65jRaX7jdGZ_FQDzVBg==(IEnumerable`1 #=qiRL7GcJARbXEDAdCiFaloRxo2oeNkdoG3jaOfwBjAnQ=, TestFrameworkFileReference[] #=qlvP2NQOH9lkmJE6SyXWqaqm9BgrZMvA2pXteAKr4oCU3pdIDfZmBDG95VXtNkxue)
at nCrunch.Core.BuildManagement.ReferencedAssemblySet..ctor(SnapshotComponent snapshotComponent, Workspace workspace, IList`1 referencedComponents)
at nCrunch.Core.BuildManagement.BuildEnvironment.Build(SnapshotComponent snapshotComponentToBuild, IList`1 referencedComponents)
at nCrunch.Core.BuildTask.DoProcessTaskAndReturnSuccessFlag()
at nCrunch.Core.Processing.ProcessingTask.ProcessTaskAndReturnSuccessFlag()
at nCrunch.Core.Processing.ProcessingQueue.#=qmw8TP7OZQi1Awa12Usj2mw==(ProcessingTask #=qbasxLAEC$whviXkzL8WKzA==)


And NCrunch is right. The directory 64 doesn't exist. There is 63 and 65 but no 64.
I don't recall deleting it either.

I sent you the report via the contact form.
Back to top
 |  Edit by user
DanHil
#19 Posted : Thursday, November 15, 2012 11:12:39 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
That last problem I reported is occurring quite frequently. It is not always the same directory that is missing, right now it is 32, before it was 82. But it is always the xunit.dll that NCrunch expects to find in that folder.

After some time (5-10 Minutes maybe) the error solves itself and the projects starts to build again.
Back to top
 |  Edit by user
DanHil
#20 Posted : Monday, November 19, 2012 11:05:28 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/12/2012(UTC)
Posts: 85

Thanks: 11 times
Was thanked: 3 time(s) in 3 post(s)
Remco, do you need any additional info on this latest problem? It is still occurring frequently.
Back to top
Users browsing this topic
Guest (2)
3 Pages123>
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.186 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download