Analyse Assembly fails on NCrunch grid nodes but I can't see why

Hi Remco,

I updated my local machine to .NET v4.5.3 to be able to run the NCrunch test runners with latest v2.11.0.23.
Now I'm facing an issue that my grid nodes have some kind of problem when analysing the asemblies. In the Processing Queue I see that those "Analyse Assembly" entries are marked with a red cross. However, as my tests run locally (according to the NCrunch Tests window), I can't see any reason why they fail. The Tests window is "all green" but the Risk/Progress bar shows a red "Build" failure.

It would be good to have some more information on the Processing Queue available to see why the analysis of the assemblies fails (the Tests window does not show any error information).

BR,
Ralf

Hi Ralf,

Try setting your Log Verbosity to Detailed. Do you see new further information in the Processing Queue window after the analysis fails?

Hi Remco,

after setting the Log verbosity to Detailed on one of the grid nodes, I see following reported:


[12:43:47.3781-NodeProcessor-12] Launching task: Analysing PostSharpRepro
[12:43:47.4111-NodeProcessor-12] Process could not be found in pool with signature matching: [ProcessSignature:
Z:\Workspaces\9180\1\bin\Debug\PostSharpRepro.dll
nCrunch.TestExecution.RemoteTaskRunner
Z:\Workspaces\9180\1\bin\Debug\PostSharpRepro.dll.config.ncrunchconfig
x86
192.168.0.35:13490
nCrunch.Core.ProcessManagement.DefaultProcessLoader
Framework453
Z:\Workspaces\9180\1\_ncrunchreferences\FluentAssertions.Core.dll
Z:\Workspaces\9180\1\_ncrunchreferences\FluentAssertions.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\Microsoft.CSharp.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\mscorlib.dll
Z:\Workspaces\9180\1\_ncrunchreferences\nunit.framework.dll
Z:\Workspaces\9180\1\_ncrunchreferences\PostSharp.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\PresentationCore.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\PresentationFramework.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Core.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Data.DataSetExtensions.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Data.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Xml.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Xml.Linq.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\WindowsBase.dll
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\System.Configuration.dll
C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server\nunit.core.DLL
C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server\nunit.core.interfaces.DLL

]
[12:43:47.4161-Core-12] Event [:nCrunch.GridNode.NodeTaskProcessor++.] is being processed on Core thread with subscriber: QueuedActionHandler.


I will send you the log file, maybe that contains more information about the situation.


BR
Ralf

Hi Ralf,

Thanks for sending the log file.

This behaviour is very strange, as the processing queue indicates that there was an error in the Analysis Task, but the logs show no evidence of this.

Probably this is related to the lack of .NET 4.5.2 task runner support.

Do you experience this only with the .NET 4.5.2 test assemblies? Are the grid nodes still able to run tests?

Hi Remco,

yes, it seems that I'm experiencing this only with .NET 4.5.2 assemblies but not with .NET 4.0 assemblies.
So the grid nodes can still run .NET 4.0 tests, but not the tests in that .NET 4.5.2 assembly.

BR, Ralf

Thanks Ralf. Are you interested in trying the new 2.12 build that went out today? This build contains a fix for the 4.5.2 task hosting .. I have a feeling it will solve this problem. This build is now available on the download page.

Hi Remco,

tested and works fine. :)

Thanks