All geek questions in one place

Build timeout after 00:15:00 minutes due to Testimpact

Recently, I keep getting this error from our build server. If we disable TestImpact, this error will not appear. We like to see the impact of our tests, so I'm looking for a different solution. Does anyone know what this means? I can not find anything about it!

Exception message: HTTP request operation completed after 00:15:00. (type TimeoutException) Trace of the exception stack: in Microsoft.TeamFoundation.Client.Channels.TfsHttpRetryChannel.Request (TfsMessage message, TimeSpan timeout) in Microsoft.TeamFoundation.Client.Channels.TfsHttpClientBase.Invoke (operation TimeSpan timeout, objects [] and exits) in Microsoft.TeamFoundation.TestImpact.Client.TestImpactServer.Microsoft.TeamFoundation.TestImpact.Client.ITestImpactServer.PublishBuildChanges (changes to Uri buildUri, CodeChange [] MPI.ationT.Item.ationf.ametation.metation.meftation.eamt. BuildIntegration.BuildActivities.GetImpactedTests.Execute (CodeActivityContext context) in System.Activities.CodeActivity.InternalExecute (ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager), System.ActivativeManager BookmarkManager BookmarkManager )

+5
source share
2 answers

Perhaps I found something that seems to fix the problem. This is what I did, and it has been working ever since:

  • I used Team Foundation Sidekick to remove all workspaces created by the user, which is used to build the application, as well as old workspaces that developers did not use anymore. It seems that the number of workspaces affects the build system.

  • I set the "Clean Workspace" to false in all the definitions of my assembly, so it will not create a new workspace every time the assembly starts.

  • I turned off the test exposure and completed the assembly. To start the test, you must have a basic fee. After the assembly was completed, I again activated the test effect.

  • I moved the reset location of the assembly to another HD to speed up the assembly (due to the IO disk). The assembly takes place in one HD, and the drop is set on another.

Now it is still working. Perhaps these steps will work for you as it worked for me. But I need more time to make sure it works.

+2
source

I think that Rafael Colucci answered your question only partially.

A test line should have a baseline built.

and below the error indicates the same

Microsoft.TeamFoundation.TestImpact.Client.TestImpactServer.Microsoft.TeamFoundation.TestImpact.Client.ITestImpactServer.PublishBuildChanges(Uri buildUri, CodeChange[] changes) at

Also, according to my knowledge, Test Impact must have a previous build for presence. In this way, he can calculate the effect on code change.

I think disabling a clean build may solve your problem. Let us know what result you get.

+1
source

Source: https://habr.com/ru/post/1205795/

More articles:


All Articles