Remove remaining CRT PAL wrappers and enable including standard headers in the CoreCLR build #98336
Build Analysis / Build Analysis
succeeded
Apr 4, 2024 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: Timeouts look like the slow mac issue, all with non-CoreCLR runtimes.
- 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.
⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis
Known Infrastructure Errors
Build Failures
runtime / Build / tvos-arm64 Release AllSubsets_NativeAOT / Send to Helix
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌The Operation will be canceled. The next steps may not contain expected logs.
-
❌The operation was canceled.
runtime / Build / maccatalyst-x64 Release AllSubsets_Mono / Send to Helix
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌The Operation will be canceled. The next steps may not contain expected logs.
-
❌The operation was canceled.
runtime / Build / osx-x64 Release AllSubsets_Mono_Minijit_RuntimeTests minijit / Send tests to Helix (Unix)
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌The Operation will be canceled. The next steps may not contain expected logs.
-
❌The operation was canceled.
Known test errors
-
❌System.IO.Tests.WorkItemExecution - System.IO.Net5Compat.Tests and System.IO.Tests suddenly exiting with error 137
-
❌WasmTestOnBrowser-System.CodeDom.Tests.WorkItemExecution - [browser][MT] TIMED_OUT but 0 was expected
-
❌WasmTestOnBrowser-System.Data.Common.Tests.WorkItemExecution - [browser][MT] TIMED_OUT but 0 was expected
Loading