NUnit for Team Build

New Post: System.TimeoutException: The request channel timed out---

TheBuilder — Wed, 17 Mar 2010 16:19:56 GMT

I was curious if anyone had seen this in the past and where (if required) they made any changes on the TFS Server (2008)? I did make some changes to the NUnitTfs.exe.config file where any timeout that was 1 minute, but that may have been overkill on my part.

For each of the following entries in the config, their timeout was increased to "00:02:00"
closeTimeout
openTimeout
sendTimeout

Best regards,
Jeremy

-=Log Excerpt=-

PublishRun
System.TimeoutException: The request channel timed out while waiting for a reply after 00:00:59.9980470. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The HTTP request to 'http://XXXXXXX:8080/Build/v1.0/PublishTestResultsBuildService2.asmx' has exceeded the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout. ---> System.Net.WebException: The operation has timed out
     at System.Net.HttpWebRequest.GetResponse()
     at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
     --- End of inner exception stack trace ---
     at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
     at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
     at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
     --- End of inner exception stack trace ---

Server stack trace:
     at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
     at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
     at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
     at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
     at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

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 KWatkins.NUnitTfs.PublishTestResultsBuildService2V1.Service2Soap.PublishRun(PublishRunRequest request)
     at KWatkins.NUnitTfs.PublishTestResultsBuildService2V1.Service2SoapClient.KWatkins.NUnitTfs.PublishTestResultsBuildService2V1.Service2Soap.PublishRun(PublishRunRequest request) in D:\Development\NUnitTFS\NUnitTFS\Service References\PublishTestResultsBuildService2V1\Reference.cs:line 2181
     at KWatkins.NUnitTfs.PublishTestResultsBuildService2V1.Service2SoapClient.PublishRun(String buildId, String resultsFile, Guid runId) in D:\Development\NUnitTFS\NUnitTFS\Service References\PublishTestResultsBuildService2V1\Reference.cs:line 2191
     at KWatkins.NUnitTfs.Publisher.PublishRun(String buildId, Guid runId) in D:\Development\NUnitTFS\NUnitTFS\Publisher.cs:line 60
     at KWatkins.NUnitTfs.Publisher.Publish() in D:\Development\NUnitTFS\NUnitTFS\Publisher.cs:line 52
     at KWatkins.NUnitTfs.Program.Main(String[] args) in D:\Development\NUnitTFS\NUnitTFS\Program.cs:line 20
C:\TFSBUILD_DIRECTORY\XXXXX\0.0\BuildType\TFSBuild.proj(461,5): error MSB3073: The command ""C:\TFSBUILD_DIRECTORY\XXXXX\BuildType\NUnitTFS.exe" -n "C:\TFSBUILD_DIRECTORY\XXXX\BuildType\nunit_results.xml" -t "xxxxx" -b "0.0_20100317.1" -f "Release" -p "Any CPU" -x "C:\TFSBUILD_DIRECTORY\XXXXX\BuildType\NUnitToMSTest.xslt"" exited with code 1.
Done executing task "Exec" -- FAILED.
Done building target "ExecuteAutoTests" in project "TFSBuild.proj" -- FAILED.
Done executing task "CallTarget" -- FAILED.
Done building target "AfterCompile" in project "TFSBuild.proj" -- FAILED.
Done Building Project "C:\TFSBUILD_DIRECTORY\XXXXX\BuildType\TFSBuild.proj" (EndToEndIteration target(s)) -- FAILED.
Deferred Messages

Source code checked in, #37852

rbanks54 — Mon, 08 Mar 2010 06:01:13 GMT

Adding a project to try and convert NCover data to MS Coverage format. This is for VS2010 format only, since only VS2010 supports the new SQLCE database format for coverage data. Much of this code is still being hacked into place as I try and figure out how things work in the VS2010 format. Feel free to jump in an continue to hack as time permits. The main work from here is populating the SQLCE database and then trying to upload it to TFS and seeing what blows up! :-)

New Post: NCover for Team Build?

CtrlAltDel — Sun, 07 Mar 2010 21:23:37 GMT

In the end I wimped out, and converted my tests to use MSTest. So far I haven't really had any problems with it, and at least I get my code coverage reports now integrated into the builds. I'm rewriting my tests to use extension methods to do the assertions, so should the need to change back to NUnit or other arise, then I just need to port the extension methods, rather than the tests themselves.

New Post: NCover for Team Build?

rbanks54 — Sun, 07 Mar 2010 21:15:25 GMT

Technically there are some major challenges that make it all-but-impossible to get working in TFS2008. I'm hoping to get it working for 2010 but it may take some time since time is something I currently lack :-(

New Post: NCover for Team Build?

MrKWatkins — Sun, 07 Mar 2010 11:21:57 GMT

I haven't done anything more on it and probably won't for a while to be honest; I'm currently spending my time on other projects.

New Post: NCover for Team Build?

esal — Fri, 05 Mar 2010 14:38:47 GMT

Any news about NCover support?

Commented Issue: URI support in NUnit output argument [6114]

pbering — Thu, 04 Mar 2010 10:40:36 GMT

I would like to be able to load a NUnit report from a URI, currently throws an exception if I try.
Comments: ** Comment from web user: pbering **

only http, and good idea for the workaround, thanks. Well I need to do this for running integration unit tests on a web based CMS system a part of my build process. I've created a HttpHandler (also a HttpModule and a WebControl) which can execute NUnit tests and return either the xml report from NUnit or a Html report to the browser. My plan is then to via the build script to launch the webdev.exe, call the url for the xml report and then use it from NUnitTFS as normal.

Commented Issue: URI support in NUnit output argument [6114]

MrKWatkins — Tue, 02 Mar 2010 11:30:57 GMT

I would like to be able to load a NUnit report from a URI, currently throws an exception if I try.
Comments: ** Comment from web user: MrKWatkins **

Presumably you just need web URLs, i.e. http or https? Should be fairly straightforward to do so I will look at adding it in when I have some free time. As a workaround you could use the WebDownload task in the MSBuild Community Tasks (http://msbuildtasks.tigris.org/) in your build script to download the file locally and then pass it to TFS.

Can I ask why you need to do this? I'd assume if you're using NUnitTFS as part of your build you'd have file system access to the unit tests.

Created Issue: URI support in NUnit output argument [6114]

pbering — Tue, 02 Mar 2010 06:27:43 GMT

I would like to be able to load a NUnit report from a URI, currently throws an exception if I try.

Source code checked in, #37475

MrKWatkins — Sun, 28 Feb 2010 14:56:34 GMT

Fixed error in exception message.

Updated Wiki: Documentation

MrKWatkins — Sun, 28 Feb 2010 14:55:49 GMT

You might find the following resources helpful:

Updated Wiki: Documentation

MrKWatkins — Sun, 28 Feb 2010 14:55:34 GMT

You might find the following resources helpful if you're having problems with NUnitTFS:

Updated Wiki: How it works

MrKWatkins — Sun, 28 Feb 2010 14:45:23 GMT

The basic process NUnitTFS follows runs thus:

Transform NUnit output. An XSL transform is used to take the output from NUnit and transform it into MSTest's .trx format. This transformation generates a unique ID on the root attribute known as the run ID.
Add build information to .trx. An XML element called <Build> is added to the .trx file after the <Times> element. This has two attributes, flavor and platform, that contain details about the build.
Retrieve build ID from TFS. A call to the QueryBuilds method on the TFS's BuildServiceV2 web service is made to retrieve details about the build. From the returned information the unique ID for the build is extracted.
Retrieve the publish service version. A call to the GetVersion method on TFS's PublishTestResultsBuildService2V1 web service. Note that this version isn't used anywhere! The MSTest executable peformed this call when publishing test results so I thought I NUnitTFS had better do it too...
Call PrepareToPublish. The PrepareToPublish method on TFS's PublishTestResultsBuildService2V1 web service is called. We pass the build ID and run ID and TFS returns a directory (on the TFS server) to save the .trx file to.
Save the .trx file. The .trx file is saved in the directory TFS gave us. The name can be specified by the -outputFile command line parameter; the default value is NUnitOutput.trx.
Call PublishRun. The PublishRun method on TFS's PublishTestResultsBuildService2V1 web service is called. We pass the build ID, run ID and name of the file we've saved. TFS then grabs the file and imports it. If something goes wrong at this stage you'll normally get the incredibly helpful Publish_GeneralFailure error.

Updated Wiki: How it works

MrKWatkins — Sun, 28 Feb 2010 14:28:52 GMT

The basic process NUnitTFS follows runs thus:

Transform NUnit output. An XSL transform is used to take the output from NUnit and transform it into MSTest's .trx format.
Add build information to .trx. An XML element called <Build> is added to the .trx file after the <Times> element. This has two attributes, flavor and platform, that contain details about the build.
Retrieve build ID from TFS. A call to the QueryBuilds method on the TFS's BuildServiceV2 web service is made to retrieve details about the build. From the returned information the unique ID for the build is extracted.

Updated Wiki: How it works

MrKWatkins — Sun, 28 Feb 2010 14:16:11 GMT

The basic process NUnitTFS follows runs thus:

Updated Wiki: Documentation

MrKWatkins — Sun, 28 Feb 2010 14:15:03 GMT

You might find the following resources helpful if you're having problems with NUnitTFS:

How it works

New Post: Problem with PrepareToPublish

Difflam — Fri, 18 Dec 2009 04:04:44 GMT

Thanks for your help!

Trying to give everyone access helped narrowing down the problem: the TFS drops folder was also setup as a shared folder, which overrode the security settings.
Everything works perfectly now.

New Post: Display the test detailed report

MrKWatkins — Thu, 17 Dec 2009 10:16:36 GMT

As detailed in my other reply to you I don't think there is anything you can do about this - you have to open the .trx file in Visual Studio to see what went wrong.

New Post: Unable to run tests on build machine

MrKWatkins — Thu, 17 Dec 2009 10:15:30 GMT

Afraid I don't know what these emails look like or are supposed to look like as I've never had our TFS set up to send them. I guess you probably won't get the results merged into any emails though. For example you don't get them merged into the build results page (I'm guessing the email is just a copy of this page) when you open it in Visual Studio either; you have to load the .trx file up in Visual Studio to find out what's gone wrong rather than have a nice way to browse through the test results. Nothing to do with this project I'm afraid - that's just how TFS works. As far as I know there is no way to customise that page with XSLT or any other way, and I would assume that's the same for the emails too.

I know the build page (and presumably the emails too) is being improved a lot for TFS 2010. It has a better summary that includes lots more information about what went wrong with the build. Hopefully this will include the info you want.

New Post: Problem with PrepareToPublish

MrKWatkins — Thu, 17 Dec 2009 10:04:24 GMT

I doubt you'll get any more information running in debug mode; the error you've given is returned by TFS. And errors returned by TFS aren't very useful... Having said that you might be able to put a breakpoint on the line where it throws the InvalidOperationException and inspect the error object returned by TFS.

Anyways if memory serves then TFS will attempt to create a folder on the build machine inside your working directory to put the result; I presume it's this step that is failing. Which implies that the TFS Service account (not the account the build service is running under, or the admin account on the build server) doesn't have permission to do that. An easy way to confirm that would be to temporarily give the Everyone group full access to the folder in question on your build server and see what happens.