Show semantic errors for loose files with top-level statements #81326
Build Analysis / Build Analysis
failed
Nov 21, 2025 in 0s
.NET Result Analysis
Details
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.
Test Failures (2 tests failed)
🔹 [All failing tests from roslyn-CI]
❌ Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.CodeRefactorings.UseRecursivePatterns.UseRecursivePatternsRefactoringTests.TestVariableDesignation [Console] [Details] [Artifacts] [0.06% 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
❌ workitem_8.WorkItemExecution [Console] [Details] [Artifacts] [1.81% 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