Unit Test Runner stuck on SendTestResults for minutes.
I was trying to profile a test that takes about a minute to run, and found that visual studio would subsequently hang for another 2-3 minutes for no apparent reason when profiling. Conveniently, the profiler itself identified what was taking so long. It seems that JetBrains.ReSharper.UnitTestRunner.MSTest11.TestCaseLog.SendTestResult(TestResult) got stuck for a very long time following the test run.
During this time, Visual Studio hangs, and if I start recklessly clicking around, it crashes. If I leave it alone, it comes back to life a few minutes later.
Any thoughts on what's causing this tremendous delay? My test doesn't generate much in the way of console or debug logs, I can't imagine what it's spending all this time transmitting in the way of a test result (the profiler data seems to live outside of this TestResult).
Is there some configuration option I can disable that will skip whatever step is occurring here?
Please sign in to leave a comment.
Hello
Are you able to share the full output of that test with us (in Unit Test Session, select the test, hit "Show Stack a Trace in a new window" icon to non-truncated output), copy all context from the window)?
Thanks!
Hi Alexander, I'll run the test again and supply you with the output when I get the chance. It is more data than I originally thought (I was only looking at console output, not debug output) It'll be maybe a couple hundred thousand rows of logs about 100 characters each.
In the mean time, are there any options that will directly or indirectly disable or circumvent the "remote/network" capabilities of the task runner when running on a single desktop and have it revert to something more performant than sockets, like using the local filesystem or memory to capture test output?
Thanks
Here's the sample output requested. It's 10,000 lines long (approx 500 kb)
https://pastebin.com/EdRpu2jd