[release/10.0] Don't assume all S_IFREG files are seekable #120839
+4
−1
Build Analysis / Build Analysis
failed
Oct 17, 2025 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
Build Failures
runtime / Build / osx-x64 Release NativeAOT / Send tests to Helix (Unix)
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25509.106/tools/Microsoft.DotNet.Helix.Sdk.MonoQueue.targets(47,5): error : Helix API does not contain an entry for OSX.1200.Amd64.Open
runtime / Build / osx-x64 Release AllSubsets_Mono_Minijit_RuntimeTests minijit / Send tests to Helix (Unix)
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25509.106/tools/Microsoft.DotNet.Helix.Sdk.MonoQueue.targets(47,5): error : Helix API does not contain an entry for OSX.1200.Amd64.Open
runtime / Build / osx-x64 Release AllSubsets_Mono_Interpreter_RuntimeTests monointerpreter / Send tests to Helix (Unix)
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25509.106/tools/Microsoft.DotNet.Helix.Sdk.MonoQueue.targets(47,5): error : Helix API does not contain an entry for OSX.1200.Amd64.Open
5 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [runtime]
Known test errors
Test Failures (2 tests failed)
🔹 [All failing tests from runtime]
❌ System.Net.WebSockets.Client.Tests.CloseTest_SharedHandler_External.CloseOutputAsync_ServerInitiated_CanReceiveAfterClose [Console] [Details] [Artifacts] [0.02% 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
❌ WasmTestOnChrome-ST-System.Net.WebSockets.Client.Tests.WorkItemExecution [Console] [Details] [Artifacts] [1.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