Skip to content

Flaky test - MSBuildServerTest #8956

@JanKrivanek

Description

@JanKrivanek

Context

System.TimeoutException : Test failed due to timeout: process 18281 is active for more than 30 sec. 
 at Microsoft.Build.UnitTests.Shared.RunnerUtilities.RunProcessAndGetOutput(String process, String parameters, Boolean& successfulExit, Boolean shellExecute, ITestOutputHelper outputHelper) in /Users/runner/work/1/s/src/UnitTests.Shared/RunnerUtilities.cs:line 110 at Microsoft.Build.UnitTests.Shared.RunnerUtilities.ExecMSBuild(String pathToMsBuildExe, String msbuildParameters, Boolean& successfulExit, Boolean shellExecute, ITestOutputHelper outputHelper) in /Users/runner/work/1/s/src/UnitTests.Shared/RunnerUtilities.cs:line 42 at Microsoft.Build.Engine.UnitTests.MSBuildServer_Tests.MSBuildServerTest() in /Users/runner/work/1/s/src/MSBuild.UnitTests/MSBuildServer_Tests.cs:line 121 at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor) at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr) 

e.g.: https://dev.azure.com/dnceng-public/public/_build/results?buildId=320229&view=ms.vss-test-web.build-test-results-tab&runId=6566008&resultId=100002&paneView=debug

Looking on the history of the test it seems to fail almost 1 PR a day

Metadata

Metadata

Assignees

Labels

Area: Our Own BuildProblems affecting the build or build infrastructure of the MSBuild repo itself.Priority:2Work that is important, but not critical for the releasebacklogtriaged

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions