[WASI] HTTP client testing #105838
Draft
[WASI] HTTP client testing #105838
Build Analysis / Build Analysis
failed
Sep 26, 2024 in 0s
.NET Result Analysis
Details
Tip
To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.
⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis
Known Infrastructure Errors
Known test errors
-
❌Workloads-ST-Wasm.Build.Tests.SatelliteAssembliesTests.WorkItemExecution - [browser] Connection refused in 127.0.0.1
-
❌Workloads-ST-Wasm.Build.Tests.SatelliteAssembliesTests.WorkItemExecution - [browser][wbt] fails with `InvalidOperationException: There is no currently active test`
-
❌Wasm.Build.Tests.SatelliteAssembliesTests.ResourcesFromMainAssembly - [browser] Connection refused in 127.0.0.1
-
❌Workloads-NoWebcil-ST-Wasm.Build.Tests.SatelliteAssembliesTests.WorkItemExecution - [browser] Connection refused in 127.0.0.1
-
❌Wasm.Build.Tests.WasmTemplateTests.RunWithDifferentAppBundleLocations - failure in Wasm.Build.Tests.WasmTemplateTests.RunWithDifferentAppBundleLocations
-
❌Workloads-NoWebcil-NoFingerprint-ST-Wasm.Build.Tests.WorkItemExecution - failure in Wasm.Build.Tests.WasmTemplateTests.RunWithDifferentAppBundleLocations
-
❌chrome-DebuggerTests.EvaluateOnCallFrameTests.WorkItemExecution - [wasm] DebuggerTests.WasmHostProvider.LaunchHostAsync
-
❌chrome-DebuggerTests.EvaluateOnCallFrameTests.WorkItemExecution - [wasm] DebuggerTests.Inspector.OpenSessionAsync
-
❌chrome-DebuggerTests.EvaluateOnCallFrameTests.WorkItemExecution - `chrome-DebuggerTests` timing out
Test Failures (217 tests failed)
🔹 [All failing tests from runtime]
- Exception Message
Assert.Equal() Failure: Values differ Expected: Aborted Actual: Open
- CallStack
at System.Net.WebSockets.Tests.WebSocketKeepAliveTests.WebSocketClient_NoServerDataSent_SendsPingAndReadsPongResponse() --- End of stack trace from previous location ---
❌ chrome-DebuggerTests.EvaluateOnCallFrame2Tests.WorkItemExecution [Console] [Details] [Artifacts] [0.75% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: DeadLetter. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configuration
❌ System.Net.Http.Functional.Tests.WorkItemExecution [Console] [Details] [Artifacts] [0.83% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configurations (2)
❌ System.Net.WebSockets.Tests.WebSocketKeepAliveTests.WebSocketClient_NoServerDataSent_SendsPingAndReadsPongResponse [Console] [Details] [Artifacts] [0.00% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configuration
Was this helpful?
Loading