Skip failing COM test#122474
Merged
Merged
Build Analysis / Build Analysis
succeeded
Dec 12, 2025 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: failures are unrelated wasm tests
- 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 test errors
-
❌Wasm.Build.Tests.LazyLoadingTests.FailOnMissingLazyAssembly - [wasm/browser] Failed to connect to socket /run/dbus/system_bus_socket
-
❌Wasm.Build.Tests.InvariantGlobalizationTests.AOT_InvariantGlobalization - [browser] Wasm.Build.Tests timeout - Timed out after 10s waiting for 'WASM EXIT'
-
❌Workloads-ST-Wasm.Build.Tests.LazyLoadingTests.WorkItemExecution - [wasm/browser] Failed to connect to socket /run/dbus/system_bus_socket
Test Failures (4 tests failed)
🔹 [All failing tests from runtime]
❌ NoFingerprint-ST-Wasm.Build.Tests.WorkItemExecution [Console] [Details] [Artifacts] [7.39% 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
❌ NoWebcil-ST-Wasm.Build.Tests.LazyLoadingTests.WorkItemExecution [Console] [Details] [Artifacts] [5.34% 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