Gallio with NCover errors in Windows 2008 x64

We have a cmdline for running our unit tests using Gallio.echo and NCover. It runs fine in windows x32, but it fails in x64. Both installers are for 64 bits.

We don't get the error always for the same test, it could run 0, 800, 1500, etc before failing. The exception we are getting looks like this: Forcibly killing the host process! Watchdog timer expired! Host process exited with code: -1

I got 2 errors in the application log, plus a bunch of successful profiling logs. We are using .net 4.0, weird thing is that it works perfectly in 32 bits. I also made sure all assemblies were compiled "any cpu".

.NET Runtime version 2.0.50727.4206 - Fatal Execution Engine Error (000007FEF98F65EA) (80131506)

and

Faulting application NCover.Console.exe, version 3.4.16.6924, time stamp 0x4d0a6149, faulting module mscorwks.dll, version 2.0.50727.4206, time stamp 0x4bf4c181, exception code 0xc0000005, fault offset 0x00000000001d599e, process id 0x%9, application start time 0x%10.

We don't get any errors running just Gallio.

Any help would be extremely appreciated. We really need to run these tests in 64 bits.

RE: Gallio with NCover errors in Windows 2008 x64

iself,

What is the path to NCover that you're using? Is it Program Files (x86)\NCover or Program Files\NCover?

Also, has anything else changed aside from the build params?

RE: Gallio with NCover errors in Windows 2008 x64

I am using "Program Files\NCover" and the 64x installs for both gallio and ncover

Note: if I run the cmdline for 3 test assemblies at a time, it works perfectly, as soon as I add more assemblies (and we have over 28) it starts failing, only for 64 bits... I cannot figure out why...

thank you!

isel

RE: Gallio with NCover errors in Windows 2008 x64

isel,

When you add tests to the profiling session and it fails, do you get an out-of-memory message? How many megs are the tests?

RE: Gallio with NCover errors in Windows 2008 x64

thank you for your reply we have 3100 tests in 28 assemblies. Test assemblies use 1.30 MB on disk, code is 3.17 MB on disk. the server has high cpu, high memory and high IO (7.5 gb ram, and we don't run anything else on it, it is just a build agent for CI) no memory exception, just this:

A fatal exception occurred while running tests. Possible causes include invalid test runner parameters and stack overflows. Gallio.Model.ModelException: An exception occurred while invoking a test driver. ---> Gallio.Runtime.Hosting.HostException: An exception occurred while connecting to the host service. ---> Gallio.Runtime.Hosting.HostException: Error attaching to the host process. ---> System.Runtime.Remoting.RemotingException: Failed to connect to an IPC Port: The system cannot find the file specified. Server stack trace: at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, Boolean secure, TokenImpersonationLevel impersonationLevel, Int32 timeout) at System.Runtime.Remoting.Channels.Ipc.ConnectionCache.GetConnection(String portName, Boolean secure, TokenImpersonationLevel level, Int32 timeout) at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream) at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Gallio.Runtime.Hosting.IHostService.Ping() at Gallio.Runtime.Hosting.IsolatedProcessHost.WaitUntilReady(IHostService hostService) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Runtime\Hosting\IsolatedProcessHost.cs:line 379 at Gallio.Runtime.Hosting.IsolatedProcessHost.AcquireRemoteHostService() in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Runtime\Hosting\IsolatedProcessHost.cs:line 119 --- End of inner exception stack trace --- at Gallio.Runtime.Hosting.IsolatedProcessHost.AcquireRemoteHostService() in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Runtime\Hosting\IsolatedProcessHost.cs:line 126 at Gallio.Runtime.Hosting.RemoteHost.AcquireHostService() in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Runtime\Hosting\RemoteHost.cs:line 68 at Gallio.Runtime.Hosting.BaseHost.Connect() in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Runtime\Hosting\BaseHost.cs:line 142 --- End of inner exception stack trace ---

RE: Gallio with NCover errors in Windows 2008 x64

rest of stack trace:

at Gallio.Runtime.Hosting.BaseHost.Connect() in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Runtime\Hosting\BaseHost.cs:line 151 at Gallio.Runtime.Hosting.IsolatedProcessHostFactory.CreateHostImpl(HostSetup hostSetup, ILogger logger) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Runtime\Hosting\IsolatedProcessHostFactory.cs:line 59 at Gallio.Model.Isolation.HostedTestIsolationContext.RunIsolatedTaskInHost (HostSetup hostSetup, StatusReporter statusReporter, Object[] args) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Model\Isolation\HostedTestIsolationContext.cs:line 111 at Gallio.Model.Isolation.HostedTestIsolationContext.RunIsolatedTaskImpl(HostSetup hostSetup, StatusReporter statusReporter, Object[] args) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Model\Isolation\HostedTestIsolationContext.cs:line 93 at Gallio.Model.DotNetTestDriver.ExploreOrRunAssembly(ITestIsolationContext testIsolationContext, TestPackage testPackage, TestExplorationOptions testExplorationOptions, TestExecutionOptions testExecutionOptions, RemoteMessageSink remoteMessageSink, IProgressMonitor progressMonitor, String taskName, FileInfo file) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Model\DotNetTestDriver.cs:line 196 at Gallio.Model.DotNetTestDriver.ExploreOrRun(ITestIsolationContext testIsolationContext, TestPackage testPackage, TestExplorationOptions testExplorationOptions, TestExecutionOptions testExecutionOptions, IMessageSink messageSink, IProgressMonitor progressMonitor, String taskName) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Model\DotNetTestDriver.cs:line 157 at Gallio.Model.DotNetTestDriver.RunImpl(ITestIsolationContext testIsolationContext, TestPackage testPackage, TestExplorationOptions testExplorationOptions, TestExecutionOptions testExecutionOptions, IMessageSink messageSink, IProgressMonitor progressMonitor) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Model\DotNetTestDriver.cs:line 148 at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.<>cDisplayClass1f.b1d(ITestDriver driver, IList1 items, Int32 driverCount) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Model\DefaultTestFrameworkManager.cs:line 466 at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.ForEachDriver[T](MultiMap2 testFrameworkPartitions, Func4 func) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Model\DefaultTestFrameworkManager.cs:line 525 --- End of inner exception stack trace --- at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.ForEachDriver[T](MultiMap2 testFrameworkPartitions, Func`4 func) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Model\DefaultTestFrameworkManager.cs:line 536 at Gallio.Model.DefaultTestFrameworkManager.FilteredTestDriver.RunImpl(ITestIsolationContext testIsolationContext, TestPackage testPackage, TestExplorationOptions testExplorationOptions, TestExecutionOptions testExecutionOptions, IMessageSink messageSink, IProgressMonitor progressMonitor) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Model\DefaultTestFrameworkManager.cs:line 458 at Gallio.Runner.DefaultTestRunner.Run(TestPackage testPackage, TestExplorationOptions testExplorationOptions, TestExecutionOptions testExecutionOptions, IProgressMonitor progressMonitor) in c:\Server\Projects\MbUnit v3.2\Work\src\Gallio\Gallio\Runner\DefaultTestRunner.cs:line 314

RE: Gallio with NCover errors in Windows 2008 x64

iself,

can you please send that trace and some example code to support@ncover.com so I can take a closer look. I'm not sure at this point what might be happening. Any other output / files you can send over that have additional details will likely be helpful. Thanks.