Skip to content

Fix the test flakiness, fixes #117172

50f99e1
Select commit
Loading
Failed to load commit list.
Merged

Fix the test flakiness #117175

Fix the test flakiness, fixes #117172
50f99e1
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Jun 30, 2025 in 2h 45m 39s

Build #20250630.42 had test failures

Details

Tests

  • Failed: 5 (0.00%)
  • Passed: 2,491,974 (98.11%)
  • Other: 48,104 (1.89%)
  • Total: 2,540,083

Annotations

Check failure on line 44 in .packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25311.107/tools/azure-pipelines/AzurePipelines.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25311.107/tools/azure-pipelines/AzurePipelines.MultiQueue.targets#L44

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25311.107/tools/azure-pipelines/AzurePipelines.MultiQueue.targets(44,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Test System.Net.Quic.Tests.MsQuicTests.CertificateCallbackThrowPropagates has failed. Check the Test tab or this console log: https://helix.dot.net/api/2019-06-17/jobs/1d873cec-e7e3-4819-9c12-b5e33f4b5c9f/workitems/System.Net.Quic.Functional.Tests/console

Check failure on line 1299 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Build log #L1299

BUILD: Error: native component build failed. Refer to the build log files for details.

Check failure on line 119 in src\coreclr\runtime.proj

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

src\coreclr\runtime.proj#L119

src\coreclr\runtime.proj(119,5): error MSB3073: (NETCORE_ENGINEERING_TELEMETRY=Build) The command ""D:\a\_work\1\s\src\mono\browser\emsdk\emsdk_env.cmd" && D:\a\_work\1\s\src\coreclr\"build-runtime.cmd" -wasm -release -ci -os browser -targetrid browser-wasm -cmakeargs "-DCLR_DOTNET_RID=browser-wasm" -cmakeargs "-DCLR_DOTNET_HOST_PATH=D:\a\_work\1\s\.dotnet\dotnet.exe" -cmakeargs "-DCDAC_BUILD_TOOL_BINARY_PATH=D:\a\_work\1\s\artifacts\bin\coreclr\browser.wasm.Release\cdac-build-tool\cdac-build-tool.dll" -cmakeargs "-DCLR_CMAKE_ICU_DIR=D:\a\_work\1\s\.packages\microsoft.netcore.runtime.icu.transport\10.0.0-preview.6.25302.1/runtimes/browser-wasm/native" -component runtime -keepnativesymbols" exited with code 1.

Check failure on line 786 in src\mono\mono.proj

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

src\mono\mono.proj#L786

src\mono\mono.proj(786,5): error MSB3073: (NETCORE_ENGINEERING_TELEMETRY=Build) The command "call "D:\a\_work\1\s\eng\native\init-vs-env.cmd" && cmake --build . --target install --config Release" exited with code 1.

Check failure on line 1 in System.Net.Quic.Tests.MsQuicTests.CertificateCallbackThrowPropagates

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

System.Net.Quic.Tests.MsQuicTests.CertificateCallbackThrowPropagates

Assert.Throws() Failure: Exception type was not an exact match
Expected: typeof(System.Security.Authentication.AuthenticationException)
Actual:   typeof(System.Net.Quic.QuicException)
---- System.Net.Quic.QuicException : The connection timed out from inactivity.
Raw output
   at System.Net.Quic.Tests.MsQuicTests.CertificateCallbackThrowPropagates() in /_/src/libraries/System.Net.Quic/tests/FunctionalTests/MsQuicTests.cs:line 373
   at System.Net.Quic.Tests.MsQuicTests.CertificateCallbackThrowPropagates() in /_/src/libraries/System.Net.Quic/tests/FunctionalTests/MsQuicTests.cs:line 380
--- End of stack trace from previous location ---
----- Inner Stack Trace -----
   at System.Net.Quic.QuicConnection.HandleEventShutdownInitiatedByTransport(_SHUTDOWN_INITIATED_BY_TRANSPORT_e__Struct& data) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicConnection.cs:line 653
   at System.Net.Quic.QuicConnection.HandleConnectionEvent(QUIC_CONNECTION_EVENT& connectionEvent) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicConnection.cs:line 767
   at System.Net.Quic.QuicConnection.NativeCallback(QUIC_HANDLE* connection, Void* context, QUIC_CONNECTION_EVENT* connectionEvent) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicConnection.cs:line 802
--- End of stack trace from previous location ---
   at System.Net.Quic.ValueTaskSource.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/Internal/ValueTaskSource.cs:line 176
   at System.Net.Quic.QuicListener.StartConnectionHandshake(QuicConnection connection, SslClientHelloInfo clientHello) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicListener.cs:line 245
   at System.Net.Quic.QuicListener.AcceptConnectionAsync(CancellationToken cancellationToken) in /_/src/libraries/System.Net.Quic/src/System/Net/Quic/QuicListener.cs:line 190
   at System.Net.Quic.Tests.MsQuicTests.<>c__DisplayClass8_0.<<CertificateCallbackThrowPropagates>b__2>d.MoveNext() in /_/src/libraries/System.Net.Quic/tests/FunctionalTests/MsQuicTests.cs:line 373
--- End of stack trace from previous location ---

Check failure on line 1 in WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.

Check failure on line 1 in WasmTestOnChrome-ST-System.Net.Http.Functional.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnChrome-ST-System.Net.Http.Functional.Tests.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.

Check failure on line 1 in WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.