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

[Broken test] Roslyn.VisualStudio.NewIntegrationTests.CSharp.CSharpGoToBase.GoToBaseFromMetadataAsSource #60386

Closed
allisonchou opened this issue Mar 25, 2022 · 2 comments · Fixed by #60458
Labels
Area-Infrastructure Disabled Test Infraswat Integration-Test Test failures in roslyn-integration-CI untriaged Issues and PRs which have not yet been triaged by a lead

Comments

@allisonchou
Copy link
Contributor

It seems GoToBaseFromMetadataAsSource broke once the integration test machines upgraded to 17.2 P2.

Error message:

System.InvalidOperationException : After updating CI to 17.2 Preview 2, the following call to ExecuteCommandAsync should has its first parameter, and uint cast, removed leaving just EditorConstants.EditorCommandID.GoToBase instead of an explicit CommandID and Guid.

Stack trace:

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)
at System.Diagnostics.Debug.Assert(Boolean condition, String message)
at Microsoft.VisualStudio.Extensibility.Testing.EditorInProcess.d__48.MoveNext() in /
/src/VisualStudio/IntegrationTest/New.IntegrationTests/InProcess/EditorInProcess.cs:line 966
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
at Roslyn.VisualStudio.NewIntegrationTests.CSharp.CSharpGoToBase.d__3.MoveNext() in /_/src/VisualStudio/IntegrationTest/New.IntegrationTests/CSharp/CSharpGoToBase.cs:line 39
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

Example build link: https://dev.azure.com/dnceng/public/_build/results?buildId=1681105&view=ms.vss-test-web.build-test-results-tab

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Issues and PRs which have not yet been triaged by a lead label Mar 25, 2022
@allisonchou
Copy link
Contributor Author

cc @sharwell

@sharwell
Copy link
Member

@allisonchou The exception message precisely indicates the fix 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure Disabled Test Infraswat Integration-Test Test failures in roslyn-integration-CI untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants