"Failed to start the tests host." - Testing a test runner.

I'm developing a test runner plugin for 7.1 with VS2012, and I can't get my test assembly to start. When I run it, I get the following 4 exceptions from TestEnvironmentAssembly:

#1: The target dispatcher JetDispatcher(CurrentAppDomainHost.ExecuteNodes:7) does not support asynchronous execution or cross-thread marshalling.

#2: The target dispatcher JetDispatcher(CurrentAppDomainHost.ExecuteNodes:7) does not support asynchronous execution or cross-thread marshalling.
#3: An item with the same key has already been added.
#4: Initial instantiation of the component TypeComponent { UpdatesNotifier, State: Corrupted } has failed. Exception has been thrown by the target of an invocation. The handler “System.Action`1[JetBrains.DataFlow.OutEventArgs`1[System.Object]]” is already sinking the signal.

I am fairly new to ReSharper plugin development, and I'm completely clueless as to why it fails. It's not related to my plugin, because it fails the same way when I run the tests in the default plugin template for VS.

Help please? :)

BR / Christian

2 comments
Comment actions Permalink
Hi Christian. It's hard to say what's wrong without some more information - a full stack trace would help, and it would be brilliant to see some code. If you'd rather email me direct, you can send me code at resharper-plugins@jetbrains.com, and we can take a look to see what's going wrong.ThanksMatt
0
Comment actions Permalink

As I said, the tests failed to start even when creating a "vanilla" plugin from the SDK templates. Nothing related to my code.

I have found what the issue was, though, and it was as I suspected a misconfiguration on my part; albeit one that I think should be mentioned in the ReadMe's. The reason was simply that the JetBrains Task Runner process was blocked by Windows Firewall. I assume that it simply prevented the process running the tests from communicating with the process running my plugin. I really think the exception handling needs improvement here though, because the error message didn't give any indication at all of the actual failure.

Anyway, everything's working for me now. Let's hope other people who stumble into the same issue find this on Google. :)

// C

0

Please sign in to leave a comment.