-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vstest.console.exe on cmd gives - An existing connection was forcibly closed #2324
Comments
Hello, thanks for reporting, are you able to reproduce this after restart? Are could you also try to reproduce this using a newer version of test console, ideally the latest one? The console is shipped in this nuget package that you can extract as a zip file, for example using 7zip. https://www.nuget.org/packages/Microsoft.TestPlatform/16.5.0 |
Something similar to this happens under MacOS, but the runner just shuts down with Stack Overflow. Using the latest version of the dotnet tools. I've been able to reproduce this problem using this project: https://github.com/carlosrfernandez/AspNet.Test.StackOverflow I believe that there's an issue with discovering assemblies at some point in the process. The sample project uses MediatR to register a message request handler and it just fails as soon as it tries to instantiate the handler using reflection. To reproduce just execute The crash reports is extensive and I can provide it if it will prove useful. Note I am using both Microsoft.TestPlatform 16.5 as well as Microsoft.NET.Test.Sdk 16.5... I'm worried that there's an underlying issue in the runtime somewhere that I can't understand yet... |
Note to self: This should be the main problem. Seem similar vstest console errors reported when testhost was not able to start because of incorrect setup. See what the exit code means, hopefully not the answer to the ultimate question of life, the universe and everything.
|
Same here. What's up with this issue? |
Description
Steps to reproduce
Run vstest.console.exe from command line using below settings and environment
Command:
.runsettings I used
Note: I have tried disabling
DataCollectors
andMaxCpuCount
but the result is same System.IO.IOException as described belowExpected behavior
Test should run
Actual behavior
I am seeing
System.Net.Sockets.SocketException
error in tracelogs. As suggested in some of questions and blogs , I have tried disablingDataCollectors
andMaxCpuCount
but the result is same as belowDiagnostic logs
Full trace logs:
Environment
OS Version : Windows Server 2012 R2 Standard
vstest.console version - 16.0.29724.72
The text was updated successfully, but these errors were encountered: