Remove isAsync flag validation from FileStream constructors #123761
Merged
Build Analysis / Build Analysis
succeeded
Jan 30, 2026 in 0s
.NET Result Analysis
Details
‼️ Build Analysis Check Result has been manually overridden
- The build analysis check result has been updated by the user for the following reason: infrastructure timeouts
- The check result has changed from Failure to Success
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.
Known Infrastructure Errors
Build Failures
runtime / Build / windows-arm64 Release NativeAOT
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌The job running on agent NetCore-Public 429 ran longer than the maximum time of 180 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
runtime / Build / windows-arm64 Release NativeAOT_Libraries
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌The job running on agent NetCore-Public 434 ran longer than the maximum time of 240 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
runtime / Build / coreclr Pri0 Runtime Tests Run windows arm64 checked
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌The job running on agent NetCore-Public 180 ran longer than the maximum time of 300 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134
Known test errors
-
❌System.Net.WebSockets.Client.Tests.CloseTest_HttpClient_External.CloseOutputAsync_ClientInitiated_CanReceive_CanClose - Android WebSocket failure
-
❌System.Net.WebSockets.Client.Tests.CloseTest_HttpClient_External.CloseOutputAsync_ClientInitiated_CanReceive_CanClose - [wasm] System.Net.WebSockets.Client.Tests.InvokerCloseTest.CloseOutputAsync_ClientInitiated_CanReceive_CanClose failing with WebSocketException
Was this helpful?
Loading