Quick Info tests fail when using new editor package versions

[dibarbet]

Found and disabled in #65795

at Roslyn.Utilities.Contract.Fail(String message, Int32 lineNumber) in /_/src/Workspaces/SharedUtilitiesAndExtensions/Compiler/Core/Utilities/Contract.cs:line 154
   at Roslyn.Utilities.Contract.ThrowIfNull[T](T value, Int32 lineNumber) in /_/src/Workspaces/SharedUtilitiesAndExtensions/Compiler/Core/Utilities/Contract.cs:line 29
   at Microsoft.VisualStudio.Extensibility.Testing.EditorInProcess.<InvokeQuickInfoAsync>d__13.MoveNext() in /_/src/VisualStudio/IntegrationTest/New.IntegrationTests/InProcess/EditorInProcess.cs:line 272
--- 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.IntegrationTests.VisualBasic.BasicQuickInfo.<International>d__4.MoveNext() in /_/src/VisualStudio/IntegrationTest/New.IntegrationTests/VisualBasic/BasicQuickInfo.cs:line 51
--- 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)

Note - these work fine in main. Only in -vs-deps with new editor package versions do these fail. Most likely related to the fact that the VS install on integration test machines is extremely old. Hopefully can re-enable with #65839

[CyrusNajmabadi]

@arkalyanms i know we've looked in the past about making it possible to get more recent versions of VS on our integration machines. But i think that work has stalled out. This is also important so we can adopt new editor APIs and have integration tests for them be updated at the same time. Right now that's often not possible.

[arunchndr]

@arkalyanms i know we've looked in the past about making it possible to get more recent versions of VS on our integration machines. But i think that work has stalled out. This is also important so we can adopt new editor APIs and have integration tests for them be updated at the same time. Right now that's often not possible.

@dibarbet is this the case where we were seeing errors in integration test scouting queues which was preventing us from promoting to a newer VS version?

[dibarbet]

Yes. THis might be fixed after this PR goes in, but may not be fixed until we can upgrade to 17.5p2. Will test after
#65846