Skip to content

Fix blame test flakiness: increase hang dump timeout to 10s

27197ae
Select commit
Loading
Failed to load commit list.
Merged

Reduce blame test flakiness: increase hang dump timeout to 10s #15590

Fix blame test flakiness: increase hang dump timeout to 10s
27197ae
Select commit
Loading
Failed to load commit list.
Azure Pipelines / microsoft.vstest failed Mar 26, 2026 in 31m 36s

Build #20260326.15 had test failures

Details

Tests

  • Failed: 2 (0.03%)
  • Passed: 7,054 (98.85%)
  • Other: 80 (1.12%)
  • Total: 7,136

Annotations

Check failure on line 0 in Microsoft.Testing.Platform

See this annotation in the file changed.

@azure-pipelines azure-pipelines / microsoft.vstest

Microsoft.Testing.Platform#L0

Microsoft.Testing.Platform(0,0): error : (NETCORE_ENGINEERING_TELEMETRY=Build) Tests failed: D:\a\_work\1\s\artifacts\log\Release\Microsoft.TestPlatform.Library.IntegrationTests_net48_x86.log [net48|x86]

Check failure on line 0 in Microsoft.Testing.Platform

See this annotation in the file changed.

@azure-pipelines azure-pipelines / microsoft.vstest

Microsoft.Testing.Platform#L0

Microsoft.Testing.Platform(0,0): error : (NETCORE_ENGINEERING_TELEMETRY=Build) Tests failed: D:\a\_work\1\s\artifacts\log\Release\Microsoft.TestPlatform.Acceptance.IntegrationTests_net9.0_x64.log [net9.0|x64]

Check failure on line 1 in Microsoft.TestPlatform.AcceptanceTests.BlameDataCollectorTests.HangDumpOnTimeout (Row: 0, Runner = net10.0, TargetFramework = net10.0, InProcess)

See this annotation in the file changed.

@azure-pipelines azure-pipelines / microsoft.vstest

Microsoft.TestPlatform.AcceptanceTests.BlameDataCollectorTests.HangDumpOnTimeout (Row: 0, Runner = net10.0, TargetFramework = net10.0, InProcess)

Expected at least 1 dump file in Attachments, but there were 0.
Raw output
   at Microsoft.TestPlatform.AcceptanceTests.BlameDataCollectorTests.ValidateDump(Int32 expectedDumpCount) in /_/test/Microsoft.TestPlatform.Acceptance.IntegrationTests/BlameDataCollectorTests.cs:line 320
   at Microsoft.TestPlatform.AcceptanceTests.BlameDataCollectorTests.HangDumpOnTimeout(RunnerInfo runnerInfo) in /_/test/Microsoft.TestPlatform.Acceptance.IntegrationTests/BlameDataCollectorTests.cs:line 146
   at InvokeStub_BlameDataCollectorTests.HangDumpOnTimeout(Object, Span`1)
   at System.Reflection.MethodBaseInvoker.InvokeWithOneArg(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

Check failure on line 1 in Microsoft.TestPlatform.Library.IntegrationTests.TranslationLayerTests.RunTests.RunTestsShouldThrowOnStackOverflowException (Row: 0, Runner = net10.0, TargetFramework = net8.0, InProcess)

See this annotation in the file changed.

@azure-pipelines azure-pipelines / microsoft.vstest

Microsoft.TestPlatform.Library.IntegrationTests.TranslationLayerTests.RunTests.RunTestsShouldThrowOnStackOverflowException (Row: 0, Runner = net10.0, TargetFramework = net8.0, InProcess)

Test method Microsoft.TestPlatform.Library.IntegrationTests.TranslationLayerTests.RunTests.RunTestsShouldThrowOnStackOverflowException threw exception:
FluentAssertions.Execution.AssertionFailedException: Expected [0] to match "The active test run was aborted. Reason: Test host process crashed : Stack overflow.*", but "The active test run was aborted. Reason: Test host process crashed" does not.
Raw output
   at FluentAssertions.Execution.FallbackTestFramework.Throw(String message)
   at FluentAssertions.Execution.AssertionChain.FailWith(Func`1 getFailureReason)
   at FluentAssertions.Primitives.StringAssertions`1.Match(String wildcardPattern, String because, Object[] becauseArgs)