dotnet/roslyn

Integration test cleanup fails to close debugger Find Source window

Aberta

#33.785 aberto em 1 de mar. de 2019

Ver no GitHubGuia do colaborador
 (4 comentários) (0 reação) (0 responsável)C# (4.257 forks)batch import
Area-InteractiveIntegration-TestInteractive-DebuggingInvestigation RequiredRegressionhelp wanted

Métricas do repositório

Stars
 (20.414 estrelas)
Métricas de merge de PR
 (Mesclagem média 6d 17h) (256 fundiu PRs em 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)

Guia do colaborador

Direção de pesquisa
Investigue o processo de limpeza do teste de integração e identifique por que a janela Localizar Fonte do depurador não fecha a tempo. Verifique os métodos WaitForDesignMode e CleanUpOpenSolution para entender o tempo limite.
Pilha de tecnologia
csharp
Domain
testing qa
Tipo Issue
Bug
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
2
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-3 horas
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
Ativo
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
Claro
Prerequisites
C#Visual StudioIntegration testing
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
50