Skip to content

[Test TFS-Git Port tool] Intermittent failures in VSIntegration tests due to remote exception at Roslyn.VSHosting.Test.RoslynActions.StartTargetAction.AddAssemblyResolveHook #230

@mavasani

Description

@mavasani

Ported from TFS WorkItem: 1115764


Repro Steps:

Main-PerCheckin-VisualStudioIntegrationTests_20150127.20 - Partially Succeeded

Open Build Report in Visual Studio | Open Build Report in Web Access

 

 

Main-PerCheckin-VisualStudioIntegrationTests_20150127.10 - Partially Succeeded

Open Build Report in Visual Studio | Open Build Report in Web Access

 


Revisions:

  1. Created by Manish Vasani (1/27/2015 10:57:51 PM)

There have been about 6 intermittent failures in VSIntegration tests (all different tests) in last week or so with the below call stack. Seems like some exception in StartTargetAction.AddAssemblyResolveHook, but there is no dump or useful info in the call stack.

 

Server stack trace: 
   at System.Runtime.Remoting.Channels.Ipc.IpcPort.Connect(String portName, Boolean secure, TokenImpersonationLevel impersonationLevel, Int32 timeout)
   at System.Runtime.Remoting.Channels.Ipc.ConnectionCache.GetConnection(String portName, Boolean secure, TokenImpersonationLevel level, Int32 timeout)
   at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.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 Roslyn.VSHosting.Test.InProcessAPI.InvokeInVS(Action action)
   at Roslyn.VSHosting.Test.RoslynActions.StartTargetAction.AddAssemblyResolveHook(TaoEngine engine) in C:\Builds\Roslyn\Main-PerCheckin-VisualStudioIntegrationTests\src\Closed\Hosting\RoslynTaoActions\Actions\VisualStudio\StartTargetAction.cs:line 31
   at Roslyn.VSHosting.Test.RoslynActions.StartTargetAction.AfterStart(TaoEngine engine) in C:\Builds\Roslyn\Main-PerCheckin-VisualStudioIntegrationTests\src\Closed\Hosting\RoslynTaoActions\Actions\VisualStudio\StartTargetAction.cs:line 23
   at Roslyn.VSHosting.Test.StartTargetAction.Execute(TaoEngine engine) in C:\Builds\Roslyn\Main-PerCheckin-VisualStudioIntegrationTests\src\Closed\Hosting\Test\Actions\VisualStudio\StartTargetAction.cs:line 93
   at Tao.Engine.DebuggableActionExecutor.Execute() in F:\dd\Omni\Tao\Tao.Engine\ActionExecutor.cs:line 139
   at Tao.Engine.DefaultActionExecutor.Execute() in F:\dd\Omni\Tao\Tao.Engine\ActionExecutor.cs:line 36


  1. Edited by Manish Vasani (1/28/2015 11:58:09 AM)

I am going to attempt a fix for this one..


  1. Edited (Active to Resolved) by Manish Vasani (1/28/2015 12:27:42 PM)

Resolved with changeset 1406179: Bug 1115764: Intermittent failures in VSIntegration tests due to remote exception at Roslyn.VSHosting.Test.RoslynActions.StartTargetAction.AddAssemblyResolveHook

We seem to be getting a remoting exception, probably because VS is not yet up. Replace InvokeInVS with InvokeOnUI call to register assembly resolver.


  1. Edited (Resolved to Closed) by Manish Vasani (1/28/2015 5:26:02 PM)

  1. Edited (Closed to Active) by Manish Vasani (1/29/2015 2:10:31 PM)

  1. Edited by Manish Vasani (1/29/2015 2:11:22 PM)

Associated with changeset 1407144: Rollback changeset 1406179 that attempted to fix bug 1115764. The fix was incorrect and the intermittent failure reproed again.


  1. Edited by Manish Vasani (1/29/2015 2:11:42 PM)

  1. Edited by Manish Vasani (1/29/2015 2:12:04 PM)

I give up and let tao experts handle this..


  1. Edited by Kevin Pilch-Bisson (1/29/2015 3:01:11 PM)

  1. Edited by Kevin Pilch-Bisson (1/30/2015 8:46:15 AM)

  1. Edited by Balaji Krishnan (1/30/2015 8:57:42 AM)

  1. Edited by Balaji Krishnan (2/2/2015 3:32:41 PM)

Associated with changeset 1408896: Tao : check if assembly exists on disk in the specified location before trying to resolve it.


Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions