Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make MaxSupportedLangVersion calculation dynamic #75795

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

syntax

7c63e3c
Select commit
Loading
Failed to load commit list.
Open

Make MaxSupportedLangVersion calculation dynamic #75795

syntax
7c63e3c
Select commit
Loading
Failed to load commit list.
Build Analysis / Build Analysis failed Nov 7, 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 (4 tests failed)

🔹 [All failing tests from roslyn-CI]

    ⚠️ 1 failing tests not displayed for this pipeline due to space limitations

    Microsoft.CodeAnalysis.Editor.UnitTests.IntelliSense.VisualBasicCompletionCommandHandlerTests.TestMatchWithTurkishIWorkaround9 [Console] [Details] [Artifacts] [5.76% failure rate]
    [ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

    Failing Configurations (2)

    Exception Message
    Assert.Equal() Failure: Strings differ
                ↓ (pos 1)
    Expected: "If"
    Actual:   "ICustomFormatter"
                ↑ (pos 1)
    CallStack
       en Xunit.Assert.Equal(String expected, String actual, Boolean ignoreCase, Boolean ignoreLineEndingDifferences, Boolean ignoreWhiteSpaceDifferences, Boolean ignoreAllWhiteSpace) en /_/src/xunit.assert/Asserts/StringAsserts.cs:línea 402
       en Microsoft.CodeAnalysis.Editor.UnitTests.IntelliSense.TestState.VB$StateMachine_50_AssertSelectedCompletionItem.MoveNext() en /_/src/EditorFeatures/TestUtilities2/Intellisense/TestState.vb:línea 470
    --- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
       en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       en Microsoft.CodeAnalysis.Editor.UnitTests.IntelliSense.VisualBasicCompletionCommandHandlerTests.VB$StateMachine_155_TestMatchWithTurkishIWorkaround9.MoveNext() en /_/src/EditorFeatures/Test2/IntelliSense/VisualBasicCompletionCommandHandlerTests.vb:línea 3168
    --- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
       en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       en Xunit.Sdk.TestInvoker`1.<>c__DisplayClass48_0.<<InvokeTestMethodAsync>b__1>d.MoveNext() en /_/src/xunit.execution/Sdk/Frameworks/Runners/TestInvoker.cs:línea 285
    --- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
       en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       en Xunit.Sdk.ExecutionTimer.<AggregateAsync>d__4.MoveNext() en /_/src/xunit.execution/Sdk/Frameworks/ExecutionTimer.cs:línea 48
    --- Fin del seguimiento de la pila de la ubicación anterior donde se produjo la excepción ---
       en System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
       en System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       en Xunit.Sdk.ExceptionAggregator.<RunAsync>d__9.MoveNext() en /_/src/xunit.core/Sdk/ExceptionAggregator.cs:línea 90
    Microsoft.CodeAnalysis.EditorFeatures2.UnitTests_59.WorkItemExecution [Console] [Details] [Artifacts] [13.45% 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.EditorFeatures2.UnitTests_72.WorkItemExecution [Console] [Details] [Artifacts] [41.05% 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

Was this helpful? Yes No