I have got a few CCNet 1.6.7981.1 services running. I have noticed that on certain runs, we are reported a build success when in reality some unit tests have failed.
The CCNet tasks look like this: <tasks> > <parallel> > <description>CleanResultFilesAndRestoreDatabase</description> > <dynamicValues /> > <environment /> > <tasks> > <msbuild> > <buildArgs>/noconsolelogger /v:quiet /clp:PerformanceSummary > /p:ApplicationUnitTestsDBName=ApplicationUnitTest-x64</buildArgs> > <description>CleanUnitTestsResultsFiles</description> > <dynamicValues /> > <environment /> > > <executable>C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe</executable> > <priority>Normal</priority> > <projectFile>UnitTests.build</projectFile> > <targets>CleanUnitTestsResultsFiles</targets> > <timeout>10800</timeout> > > <workingDirectory>C:\Projects\Application\Checkout\CURRENT\Build\</workingDirectory> > </msbuild> > <msbuild> > <buildArgs>/noconsolelogger /v:quiet /clp:PerformanceSummary > /p:ApplicationUnitTestsDBName=ApplicationUnitTest-x64</buildArgs> > <description>RestoreUnitTestsDatabase</description> > <dynamicValues /> > <environment /> > > <executable>C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe</executable> > <priority>Normal</priority> > <projectFile>UnitTests.build</projectFile> > <targets>RestoreUnitTestsDatabase</targets> > <timeout>10800</timeout> > > <workingDirectory>C:\Projects\Application\Checkout\CURRENT\Build\</workingDirectory> > </msbuild> > </tasks> > </parallel> > <sequential> > <continueOnFailure>True</continueOnFailure> > <dynamicValues /> > <environment /> > <tasks> > <msbuild> > <buildArgs>/noconsolelogger /v:quiet /clp:PerformanceSummary > /p:ApplicationUnitTestsDBName=ApplicationUnitTest-x64</buildArgs> > <description>CompanyApplicationIntegrationUnitTests</description> > <dynamicValues /> > <environment /> > > <executable>C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe</executable> > <priority>Normal</priority> > <projectFile>UnitTests.build</projectFile> > <targets>CompanyApplicationIntegrationUnitTests</targets> > <timeout>10800</timeout> > > <workingDirectory>C:\Projects\Application\Checkout\CURRENT\Build\</workingDirectory> > </msbuild> > <parallel> > <dynamicValues /> > <environment /> > <tasks> > <msbuild> > <buildArgs>/noconsolelogger /v:quiet /clp:PerformanceSummary > /p:ApplicationUnitTestsDBName=ApplicationUnitTest-x64</buildArgs> > <description>CompanyApplicationCommonUnitTests</description> > <dynamicValues /> > <environment /> > > <executable>C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe</executable> > <priority>Normal</priority> > <projectFile>UnitTests.build</projectFile> > <targets>CompanyApplicationCommonUnitTests</targets> > <timeout>10800</timeout> > > <workingDirectory>C:\Projects\Application\Checkout\CURRENT\Build\</workingDirectory> > </msbuild> > <msbuild> > <buildArgs>/noconsolelogger /v:quiet /clp:PerformanceSummary > /p:ApplicationUnitTestsDBName=ApplicationUnitTest-x64</buildArgs> > <description>CompanyApplicationCoreUnitTests</description> > <dynamicValues /> > <environment /> > > <executable>C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe</executable> > <priority>Normal</priority> > <projectFile>UnitTests.build</projectFile> > <targets>CompanyApplicationCoreUnitTests</targets> > <timeout>10800</timeout> > > <workingDirectory>C:\Projects\Application\Checkout\CURRENT\Build\</workingDirectory> > </msbuild> > </tasks> > </parallel> > <msbuild> > <buildArgs>/noconsolelogger /v:quiet /clp:PerformanceSummary > /p:ApplicationUnitTestsDBName=ApplicationUnitTest-x64</buildArgs> > > <description>CompanyApplicationServicesUnitTestsNotSlow</description> > <dynamicValues /> > <environment /> > > <executable>C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe</executable> > <priority>Normal</priority> > <projectFile>UnitTests.build</projectFile> > <targets>CompanyApplicationServicesUnitTestsNotSlow</targets> > <timeout>10800</timeout> > > <workingDirectory>C:\Projects\Application\Checkout\CURRENT\Build\</workingDirectory> > </msbuild> > <msbuild> > <buildArgs>/noconsolelogger /v:quiet /clp:PerformanceSummary > /p:ApplicationUnitTestsDBName=ApplicationUnitTest-x64</buildArgs> > > <description>CompanyApplicationPresentationUnitTests</description> > <dynamicValues /> > <environment /> > > <executable>C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe</executable> > <priority>Normal</priority> > <projectFile>UnitTests.build</projectFile> > <targets>CompanyApplicationPresentationUnitTests</targets> > <timeout>10800</timeout> > > <workingDirectory>C:\Projects\Application\Checkout\CURRENT\Build\</workingDirectory> > </msbuild> > <msbuild> > <buildArgs>/noconsolelogger /v:quiet /clp:PerformanceSummary > /p:ApplicationUnitTestsDBName=ApplicationUnitTest-x64</buildArgs> > <description>CompanyApplicationWebServicesUnitTests</description> > <dynamicValues /> > <environment /> > > <executable>C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe</executable> > <priority>Normal</priority> > <projectFile>UnitTests.build</projectFile> > <targets>CompanyApplicationWebServicesUnitTests</targets> > <timeout>10800</timeout> > > <workingDirectory>C:\Projects\Application\Checkout\CURRENT\Build\</workingDirectory> > </msbuild> > <msbuild> > <buildArgs>/noconsolelogger /v:quiet /clp:PerformanceSummary > /p:ApplicationUnitTestsDBName=ApplicationUnitTest-x64</buildArgs> > <description>CompanyApplicationWebUnitTests</description> > <dynamicValues /> > <environment /> > > <executable>C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe</executable> > <priority>Normal</priority> > <projectFile>UnitTests.build</projectFile> > <targets>CompanyApplicationWebUnitTests</targets> > <timeout>10800</timeout> > > <workingDirectory>C:\Projects\Application\Checkout\CURRENT\Build\</workingDirectory> > </msbuild> > </tasks> > </sequential> > </tasks> We can see this in the logs: <msbuild startTime="10/12/2012 11:16:53" elapsedTime="00:00:02" > elapsedSeconds="2" success="true" /> > <msbuild startTime="10/12/2012 11:16:53" elapsedTime="00:00:14" > elapsedSeconds="14" success="true" /> > <msbuild startTime="10/12/2012 11:17:08" elapsedTime="00:00:06" > elapsedSeconds="6" success="true" /> > <msbuild startTime="10/12/2012 11:17:15" elapsedTime="00:00:16" > elapsedSeconds="16" success="true" /> > <msbuild startTime="10/12/2012 11:17:15" elapsedTime="00:00:28" > elapsedSeconds="28" success="true" /> > <msbuild startTime="10/12/2012 11:17:43" elapsedTime="00:00:50" > elapsedSeconds="3170" success="*true*"> <warning code="MSB3073" line="0" > column="0" timeStamp="10/12/2012 12:10:33"><![CDATA[The command > ""C:\Projects\Application\Checkout\Third > Party\NUnit.org\NUnit\2.5.7.10213\nunit-console.exe" /nologo > /timeout=120000 /noshadow Company.Application.Services.UnitTests.dll > /exclude:WatiN,WinForms,WebService,Slow" > <warning code="MSB3073" line="0" column="0" timeStamp="10/12/2012 > 12:10:33"><![CDATA[The command ""C:\Projects\Application\Checkout\Third > Party\NUnit.org\NUnit\2.5.7.10213\nunit-console.exe" /nologo > /timeout=120000 /noshadow Company.Application.Services.UnitTests.dll > /exclude:WatiN,WinForms,WebService,Slow" *exited with code > -100*.]]></warning> > </msbuild> <msbuild startTime="10/12/2012 12:10:33" elapsedTime="00:00:55" > elapsedSeconds="55" success="true" /> <msbuild startTime="10/12/2012 > 12:11:28" elapsedTime="00:00:40" elapsedSeconds="220" success="true" /> > <msbuild startTime="10/12/2012 12:15:08" elapsedTime="00:00:52" > elapsedSeconds="112" success="true" /> > </msbuild> > <msbuild startTime="10/12/2012 12:10:33" elapsedTime="00:00:55" > elapsedSeconds="55" success="true" /> > <msbuild startTime="10/12/2012 12:11:28" elapsedTime="00:00:40" > elapsedSeconds="220" success="true" /> > <msbuild startTime="10/12/2012 12:15:08" elapsedTime="00:00:52" > elapsedSeconds="112" success="true" /> Am I right to conjecture this is a bug in this version of CCNet? Or is it something in our configuration? I did look around to see if this has been already reported or fixed, but I couldn't find it yet. Kind regards, Ale
