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.

Sign up for GitHub

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

Remove unused OmniSharp extension method #72154

Merged
merged 1 commit into from
Feb 17, 2024

Remove unused OmniSharp extension method

8c2367c
Select commit
Loading
Failed to load commit list.
Merged

Remove unused OmniSharp extension method #72154

Remove unused OmniSharp extension method
8c2367c
Select commit
Loading
Failed to load commit list.
Azure Pipelines / roslyn-CI succeeded Feb 17, 2024 in 42m 57s

Build #20240216.77 had test failures

1 errors / 31 warnings

Details

Tests

  • Failed: 2 (0.00%)
  • Passed: 908,898 (98.77%)
  • Other: 11,287 (1.23%)
  • Total: 920,187

Annotations

Check failure on line 109 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / roslyn-CI

Build log #L109 

The process cannot access the file 'D:\a\_work\1\s\artifacts\log\Release\Build.Server.log' because it is being used by another process.

Check failure on line 1 in Microsoft.CodeAnalysis.Editor.UnitTests.IntelliSense.VisualBasicCompletionCommandHandlerTests.TestCompletionInLinkedFiles

See this annotation in the file changed.

@azure-pipelines azure-pipelines / roslyn-CI

Microsoft.CodeAnalysis.Editor.UnitTests.IntelliSense.VisualBasicCompletionCommandHandlerTests.TestCompletionInLinkedFiles 

Assert.NotNull() Failure
Raw output 
   at Microsoft.CodeAnalysis.Editor.UnitTests.IntelliSense.TestState.VB$StateMachine_50_AssertSelectedCompletionItem.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.CodeAnalysis.Editor.UnitTests.IntelliSense.VisualBasicCompletionCommandHandlerTests.VB$StateMachine_97_TestCompletionInLinkedFiles.MoveNext() in /_/src/EditorFeatures/Test2/IntelliSense/VisualBasicCompletionCommandHandlerTests.vb:line 2065
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

Check failure on line 1 in Microsoft.CodeAnalysis.EditorFeatures2.UnitTests_31.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / roslyn-CI

Microsoft.CodeAnalysis.EditorFeatures2.UnitTests_31.WorkItemExecution 

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.
View more details on Azure Pipelines