Ensure we don't do duplicate checks for various multi-reg paths #128117
+23
−27
Build Analysis / Build Analysis
succeeded
May 14, 2026 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: https://github.com/dotnet/dnceng/issues/6487
- 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
Test Failures (1 tests failed)
🔹 [All failing tests from runtime]
❌ Regression_7.WorkItemExecution [Console] [Details] [Artifacts] [0.36% failure rate]
-
[ 🚧 Create issue against infrastructure team] [ 📄 Create issue in this repo]
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