Re: [NAnt-users] nunit-console executes, but does not return control to NAnt

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Hmm, some further digging suggests it may be some badly written multi-threading tests : http://stackoverflow.com/questions/2433700/nunit-console-exe-hangs-after-finishing-test-run
I'll fix up the tests and see what happens.

From: David Keaveny
Sent: Thursday, 10 June 2010 10:23 AM
To: nan...@li...
Subject: nunit-console executes, but does not return control to NAnt

I've inherited a set of build scripts that run under CC.NET, and I'm having problems with using the NUnit test runner. Nant invokes it without problem, and the tests run, writing their output to the designated output file, but then the nunit-console.exe fails to return control to Nant, which just sits there until it reaches its timeout period.

I'm currently running Nant v0.9 and NUnit v2.5.5, although the build was originally running v0.85 and v2.2 respectively and demonstrating the same behaviour.

The tests are invoked thusly:

<exec program="nunit-console.exe" basedir="\Source\BuildProcess\tools\NUnit\v2.5.5.10112" >
                <arg value="\Tests\MyTests.dll" />
                <arg value="/xml:\Out\Output.xml" />
</exec>

And the CC.NET logs report:

2010-06-10 09:42:39,681 [32:DEBUG] [MyProject.Components D:\Source\BuildProcess\bin\nant.exe]      [exec] 51) Parent Failure : MyProject.Components.UnitTests.StatisticsTest.TestSearchStatistics
2010-06-10 09:42:39,681 [32:DEBUG] [MyProject.Components D:\Source\BuildProcess\bin\nant.exe]      [exec]    TestFixtureSetUp failed in StatisticsTest
2010-06-10 09:42:39,681 [32:DEBUG] [MyProject.Components D:\Source\BuildProcess\bin\nant.exe]      [exec]
2010-06-10 09:49:23,238 [MyProject.Components:WARN] Process timed out: D:\Source\BuildProcess\bin\nant.exe -buildfile:D:\Source\BuildProcess\build\build.build -logger:NAnt.Core.XmlLogger -logfile:d:\CruiseControl\MyProject.Components\nant-results-6656e906-f0ad-4e4e-8208-bb312a3c9d5a.xml -listener:NAnt.Core.DefaultLogger -D:CCNetArtifactDirectory=d:\CruiseControl\MyProject.Components -D:CCNetBuildCondition=ForceBuild -D:CCNetBuildDate=2010-06-10 -D:CCNetBuildTime=09:39:21 -D:CCNetFailureUsers= -D:CCNetIntegrationStatus=Unknown -D:CCNetLabel=136 -D:CCNetLastIntegrationStatus=Failure -D:CCNetListenerFile=d:\CruiseControl\MyProject.Components\MyProject.Components_ListenFile.xml -D:CCNetModifyingUsers= -D:CCNetNumericLabel=136 -D:CCNetProject=MyProject.Components -D:CCNetProjectUrl=http://devbuild/ccnet/default.aspx?_action_ViewLatestBuildReport=true&server=local&project=MyProject.Components -D:CCNetRequestSource=DEVBUILD -D:CCNetWorkingDirectory=d:\Source\Domain MyProject.Components.ContinuousBuild2.  Process id: 5980. This process will now be killed.
2010-06-10 09:49:23,238 [MyProject.Components:DEBUG] Sending kill to process 5980 and waiting 10 seconds for it to exit.
2010-06-10 09:49:24,910 [MyProject.Components:WARN] The process has been killed: 5980
2010-06-10 09:49:24,910 [MyProject.Components:DEBUG] Exception caught: NAnt process timed out (after 600 seconds)

You can see that the tests finish at 09:42:39, but nothing then happens until 09:49:23 when the timeout period hits. Has anyone else experience this sort of timeout problem?

Many thanks,
David Keaveny

The information contained in this e-mail message and any accompanying files is or may be confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail is subject to copyright. No part of it should be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. Fairfax does not guarantee the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore Fairfax does not accept legal responsibility for the contents of this message or attached files.