-
Notifications
You must be signed in to change notification settings - Fork 327
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
17.11+ System.IO.IOException: Connection forcibly closed by remote host #10402
Comments
Hello, this error is a red herring, it means that the other process died unexpectedly. Please collect diagnostic logs and post them here: https://github.com/Microsoft/vstest/blob/main/docs/diagnose.md Or if they contain private information, please create a visual studio feedback issue and upload them there, you can share logs there privately. If you are unable to share them, please look into the .host..log for exceptions. Please start from the bottom, it should be the last exception that happens. OR if you see just heartbeat and then the process dies, then it was killed externally. |
@nohwnd I can confirm that this error appears after I upgraded the version from 17.9.0 to 17.11.1 when this error does not appear before the update with same set of test cases |
Can you provide the diag logs I was asking for above, please? |
Created Microsoft feedback ticket and attached logs in private https://developercommunity.visualstudio.com/t/MicrosoftNETTestSDK-1711-SystemIO/10840657 |
Today I was also able to see that with 17.10.0, this exception did not occur on the same branch. |
Issue Description
After upgrading
Microsoft.NET.Test.Sdk
from version17.10.0
to17.11.0
, our AzureDevOps test pipeline task encounters aSystem.IO.IOException
at the very beginning of the run.Steps to Reproduce
Use
Microsoft.NET.Test.Sdk
version17.11.0
or aboveRun
dotnet test
via theDotNetCoreCLI@2
in an AzureDevOps pipeline:Expected Behavior
Test run as expected with no IO exception at the start
Actual Behavior
Error seen in the AzureDevops test pipeline log:
Environment
Windows Server 2016 inside a AzureDevOps agent pipeline job
Additional Notes
This is not happening on version
17.10.0
or presumably earlier. Seems to be happening at ProxyDataCollectionManager.cs line 288I'm not sure what is trying to be written/connected when the issue happens
The text was updated successfully, but these errors were encountered: