[wasm] Dispose Xunit ToolCommand #108319
Merged
[wasm] Dispose Xunit ToolCommand #108319
Build Analysis / Build Analysis
succeeded
Sep 30, 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: the failing test is timeout with no log, typical for CI builds on windows. We cannot catch it with active issue
- 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
-
❌Wasm.Build.Tests.TestAppScenarios.LazyLoadingTests.LoadLazyAssemblyBeforeItIsNeeded - [Wasm][Test Failure] LoadLazyAssemblyBeforeItIsNeeded(lazyLoadingTestExtension: "wasm", allLazyLoadingTestExtensions: ["wasm", "dll", "NoExtension"])
-
❌Workloads-NoWebcil-NoFingerprint-ST-Wasm.Build.Tests.WorkItemExecution - [Wasm][Test Failure] LoadLazyAssemblyBeforeItIsNeeded(lazyLoadingTestExtension: "wasm", allLazyLoadingTestExtensions: ["wasm", "dll", "NoExtension"])
-
❌Wasm.Build.Tests.TestAppScenarios.LazyLoadingTests.FailOnMissingLazyAssembly - SpawnBrowserAsync on Windows
-
❌Wasm.Build.Tests.TestAppScenarios.LazyLoadingTests.LoadLazyAssemblyBeforeItIsNeeded - SpawnBrowserAsync on Windows
-
❌Wasm.Build.Tests.WasmTemplateTests.RunWithDifferentAppBundleLocations - failure in Wasm.Build.Tests.WasmTemplateTests.RunWithDifferentAppBundleLocations
-
❌Workloads-ST-Wasm.Build.Tests.TestAppScenarios.LazyLoadingTests.WorkItemExecution - SpawnBrowserAsync on Windows
-
❌Workloads-ST-Wasm.Build.Tests.WasmTemplateTests.WorkItemExecution - failure in Wasm.Build.Tests.WasmTemplateTests.RunWithDifferentAppBundleLocations
Test Failures (2 tests failed)
🔹 [All failing tests from runtime]
❌ Wasm.Build.Tests.Blazor.MiscTests3.WithDllImportInMainAssembly [Console] [Details] [Artifacts] [2.71% 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
Loading