VB Overload Resolution Priority - handle operators and respect language version #75941
Build Analysis / Build Analysis
failed
Nov 16, 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.
Build Failures
roslyn-CI / Unix_Debug_CoreClr / Test_Linux_Debug / Test
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌Bash failed with error: 1
-
❌Bash exited with return code: 1
Test Failures (16 tests failed)
🔹 [All failing tests from roslyn-CI]
- Test_Linux_Debug_Ubuntu.2004.Amd64.Open
- Test_Windows_CoreClr_Debug_Windows.10.Amd64.Open
- Test_Windows_CoreClr_IOperation_Debug_Windows.10.Amd64.Open
- Test_Windows_CoreClr_UsedAssemblies_Debug_Windows.10.Amd64.Open
- Test_Windows_CoreClr_Release_Windows.10.Amd64.Open
- Test_Windows_Desktop_Debug_64_Windows.10.Amd64.Open
- Test_Windows_Desktop_Spanish_Release_64_Windows.10.Amd64.Server2022.ES.Open
- Test_Windows_Desktop_Release_32_Windows.10.Amd64.Open
- Exception Message
System.InvalidOperationException : Unexpected value 'OverloadResolutionPriority' of type 'Microsoft.CodeAnalysis.VisualBasic.Syntax.InternalSyntax.Feature'
- CallStack
at Microsoft.CodeAnalysis.ThrowingTraceListener.Fail(String message, String detailMessage) in /_/src/Compilers/Test/Core/ThrowingTraceListener.cs:line 26 at System.Diagnostics.TraceInternal.Fail(String message, String detailMessage) at System.Diagnostics.Debug.Fail(String message, String detailMessage) at Roslyn.Utilities.ExceptionUtilities.UnexpectedValue(Object o) in /_/src/Compilers/Core/Portable/InternalUtilities/ExceptionUtilities.cs:line 22 at Microsoft.CodeAnalysis.VisualBasic.Syntax.InternalSyntax.FeatureExtensions.GetResourceId(Feature feature) in /_/src/Compilers/VisualBasic/Portable/Parser/ParserFeature.vb:line 191 at Microsoft.CodeAnalysis.VisualBasic.UnitTests.DiagnosticTests.Features() in /_/src/Compilers/VisualBasic/Test/Semantic/Diagnostics/DiagnosticTests.vb:line 67 at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor) at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
❌ Microsoft.CodeAnalysis.VisualBasic.Semantic.UnitTests_119.WorkItemExecution [Console] [Details] [Artifacts] [0.64% 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]
❌ Microsoft.CodeAnalysis.VisualBasic.Semantic.UnitTests_162.WorkItemExecution [Console] [Details] [Artifacts] [0.39% 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 Configurations (2)
❌ Microsoft.CodeAnalysis.VisualBasic.Semantic.UnitTests_252.WorkItemExecution [Console] [Details] [Artifacts] [0.53% 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]
❌ Microsoft.CodeAnalysis.VisualBasic.UnitTests.DiagnosticTests.Features [Console] [Details] [Artifacts] [0.02% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configurations (8)
Was this helpful?
Loading