[release/8.0-staging] Update dependencies from dotnet/emsdk #103427
Closed
Build Analysis / Build Analysis
failed
Jul 2, 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.
Test Failures (4 tests failed)
🔹 [All failing tests from runtime]
- Exception Message
Assert.Throws() Failure Expected: typeof(System.Exception) Actual: (No exception was thrown)
- CallStack
at System.Net.Http.WinHttpHandlerFunctional.Tests.BidirectionStreamingTest.BackwardsCompatibility_DowngradeToHttp11() in /_/src/libraries/System.Net.Http.WinHttpHandler/tests/FunctionalTests/BidirectionStreamingTest.cs:line 345 --- End of stack trace from previous location ---
❌ System.Net.Http.WinHttpHandlerFunctional.Tests.BidirectionStreamingTest.BackwardsCompatibility_DowngradeToHttp11 [Console] [Details] [Artifacts] [5.91% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configurations (2)
❌ Wasm.Build.Tests.WasmTemplateTests.RunWithDifferentAppBundleLocations [Console] [Details] [Artifacts] [1.57% 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 Configuration
❌ Workloads-NoWebcil-Wasm.Build.Tests.WasmTemplateTests.WorkItemExecution [Console] [Details] [Artifacts] [15.00% 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 Configuration
Was this helpful?
Loading