Fix style binding failure in Document Outline #74263
Merged
Build Analysis / Build Analysis
failed
Jul 8, 2024 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 (5 tests failed)
🔹 [All failing tests from roslyn-CI]
- Exception Message
Expected: Semantic search query terminated with exception Actual: Semantic search query failed to compile
Expected: True
Actual: False- CallStack
at Roslyn.Test.Utilities.AssertEx.Equal(String expected, String actual) in /_/src/Compilers/Test/Core/Assert/AssertEx.cs:line 206 at Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.SemanticSearch.CSharpSemanticSearchServiceTests.Exception() in /_/src/Features/CSharpTest/SemanticSearch/CSharpSemanticSearchServiceTests.cs:line 236 --- End of stack trace from previous location ---
- Exception Message
Assert.Throws() Failure Expected: typeof(System.OperationCanceledException) Actual: (No exception was thrown)
- CallStack
at Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.SemanticSearch.CSharpSemanticSearchServiceTests.ForcedCancellation() in /_/src/Features/CSharpTest/SemanticSearch/CSharpSemanticSearchServiceTests.cs:line 130 --- End of stack trace from previous location ---
- Exception Message
Assert.Null() Failure Expected: (null) Actual: Semantic search query failed to compile
- CallStack
at Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.SemanticSearch.CSharpSemanticSearchServiceTests.SimpleQuery() in /_/src/Features/CSharpTest/SemanticSearch/CSharpSemanticSearchServiceTests.cs:line 82 --- End of stack trace from previous location ---
- Exception Message
Expected: Semantic search query terminated with exception Actual: Semantic search query failed to compile
Expected: True
Actual: False- CallStack
at Roslyn.Test.Utilities.AssertEx.Equal(String expected, String actual) in /_/src/Compilers/Test/Core/Assert/AssertEx.cs:line 206 at Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.SemanticSearch.CSharpSemanticSearchServiceTests.StackOverflow() in /_/src/Features/CSharpTest/SemanticSearch/CSharpSemanticSearchServiceTests.cs:line 178 --- End of stack trace from previous location ---
❌ Microsoft.CodeAnalysis.CSharp.Features.UnitTests_12.WorkItemExecution [Console] [Details] [Artifacts] [1.32% 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
❌ Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.SemanticSearch.CSharpSemanticSearchServiceTests.Exception [Console] [Details] [Artifacts] [0.13% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configuration
❌ Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.SemanticSearch.CSharpSemanticSearchServiceTests.ForcedCancellation [Console] [Details] [Artifacts] [0.13% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configuration
❌ Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.SemanticSearch.CSharpSemanticSearchServiceTests.SimpleQuery [Console] [Details] [Artifacts] [0.13% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configuration
❌ Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.SemanticSearch.CSharpSemanticSearchServiceTests.StackOverflow [Console] [Details] [Artifacts] [0.13% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configuration
Was this helpful?
Loading