dotnet/roslyn

Integration test cleanup fails to close debugger Find Source window

Open

#33,785 opened on Mar 1, 2019

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C# (4,257 forks)batch import
Area-InteractiveIntegration-TestInteractive-DebuggingInvestigation RequiredRegressionhelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

image

System.TimeoutException: Failed to enter design mode in a timely manner.

Server stack trace: 
   at Microsoft.VisualStudio.IntegrationTest.Utilities.InProcess.SolutionExplorer_InProc.WaitForDesignMode()
   at Microsoft.VisualStudio.IntegrationTest.Utilities.InProcess.SolutionExplorer_InProc.CleanUpOpenSolution()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.VisualStudio.IntegrationTest.Utilities.InProcess.SolutionExplorer_InProc.CleanUpOpenSolution()
   at Microsoft.VisualStudio.IntegrationTest.Utilities.VisualStudioInstance.CleanUp() in /_/src/VisualStudio/IntegrationTest/TestUtilities/VisualStudioInstance.cs:line 210
   at Microsoft.VisualStudio.IntegrationTest.Utilities.VisualStudioInstance.Close(Boolean exitHostProcess) in /_/src/VisualStudio/IntegrationTest/TestUtilities/VisualStudioInstance.cs:line 244
   at Microsoft.VisualStudio.IntegrationTest.Utilities.VisualStudioInstanceFactory.<UpdateCurrentlyRunningInstanceAsync>d__12.MoveNext() in /_/src/VisualStudio/IntegrationTest/TestUtilities/VisualStudioInstanceFactory.cs:line 204
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task).GetType().Name

Server stack trace: 
   at Microsoft.VisualStudio.IntegrationTest.Utilities.InProcess.SolutionExplorer_InProc.WaitForDesignMode()
   at Microsoft.VisualStudio.IntegrationTest.Utilities.InProcess.SolutionExplorer_InProc.CleanUpOpenSolution()
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.VisualStudio.IntegrationTest.Utilities.InProcess.SolutionExplorer_InProc.CleanUpOpenSolution()
   at Microsoft.VisualStudio.IntegrationTest.Utilities.VisualStudioInstance.CleanUp() in /_/src/VisualStudio/IntegrationTest/TestUtilities/VisualStudioInstance.cs:line 210
   at Microsoft.VisualStudio.IntegrationTest.Utilities.VisualStudioInstance.Close(Boolean exitHostProcess) in /_/src/VisualStudio/IntegrationTest/TestUtilities/VisualStudioInstance.cs:line 244
   at Microsoft.VisualStudio.IntegrationTest.Utilities.VisualStudioInstanceFactory.<UpdateCurrentlyRunningInstanceAsync>d__12.MoveNext() in /_/src/VisualStudio/IntegrationTest/TestUtilities/VisualStudioInstanceFactory.cs:line 204
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

Contributor guide

Research direction
Investigate the integration test cleanup process and identify why the debugger Find Source window does not close in time. Look at the WaitForDesignMode method and the CleanUpOpenSolution method to understand the timeout.
Tech stack
csharp
Domain
testing qa
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Visual StudioIntegration testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50