[wasi] enable WASMTIME_BACKTRACE_DETAILS #104446
Merged
Build Analysis / Build Analysis
succeeded
Jul 5, 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: CI is stuck on unrelated infra 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
Build Failures
runtime / Build / browser-wasm linux Release LibraryTests_Threading
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌
-
❌Agent failed with exception: The machine running request 306ed94a-7a68-4ea5-ace4-2b19bf1c8257 restarted. Azure DevOps can't recover from restarts.
Known test errors
Test Failures (2 tests failed)
🔹 [All failing tests from runtime]
❌ WasmTestOnChrome-MT-System.Threading.Tasks.Tests.WorkItemExecution [Console] [Details] [Artifacts] [94.02% 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
❌ WasmTestOnFirefox-MT-System.Threading.Tests.WorkItemExecution [Console] [Details] [Artifacts] [94.15% 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