Move src/native libraries that are shared between runtime builds to be targets-driven #103184
Build Analysis / Build Analysis
succeeded
Jun 24, 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: Wasm firefox timeout seems unrelated.
- 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 test errors
-
❌System.Runtime.Tests.WorkItemExecution - Failed USB connection via port 54050, error 61, in tvOS arm64 Release AllSubsets_Mono
-
❌System.Runtime.Tests.WorkItemExecution - Failed USB connection via port 54050, error 61, in tvOS arm64 Release AllSubsets_Mono
-
❌WasmTestOnChrome-MT-System.Buffers.Tests.WorkItemExecution - Wasm test failure: Tests timed out. Killing driver service
-
❌WasmTestOnChrome-MT-System.Buffers.Tests.WorkItemExecution - System.Buffers.Tests timeout on wasm MT
-
❌WasmTestOnChrome-MT-System.Threading.Tasks.Tests.WorkItemExecution - Wasm test failure: Tests timed out. Killing driver service
Test Failures (1 tests failed)
🔹 [All failing tests from runtime]
❌ WasmTestOnFirefox-MT-System.Threading.Tasks.Tests.WorkItemExecution [Console] [Details] [Artifacts] [81.76% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: Timeout. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configuration
Was this helpful?
Loading