You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading Microsoft.NET.Test.Sdk from version 17.10.0 to 17.11.0, our AzureDevOps test pipeline task encounters a System.IO.IOException at the very beginning of the run.
Steps to Reproduce
Use Microsoft.NET.Test.Sdk version 17.11.0 or above
Run dotnet test via the DotNetCoreCLI@2 in an AzureDevOps pipeline:
- task: DotNetCoreCLI@2
displayName: dotnet test
inputs:
command: test
projects: <project solution>
Expected Behavior
Test run as expected with no IO exception at the start
Actual Behavior
Error seen in the AzureDevops test pipeline log:
System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host..
---> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 count)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.BufferedStream.Flush()
at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.SocketCommunicationManager.WriteAndFlushToChannel(String rawMessage) in /_/src/Microsoft.TestPlatform.CommunicationUtilities/SocketCommunicationManager.cs:line 413
at Microsoft.VisualStudio.TestPlatform.CommunicationUtilities.DataCollection.DataCollectionRequestSender.SendAfterTestRunEndAndGetResult(ITestMessageEventHandler runEventsHandler, Boolean isCancelled) in /_/src/Microsoft.TestPlatform.CommunicationUtilities/DataCollectionRequestSender.cs:line 155
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.DataCollection.ProxyDataCollectionManager.<>c__DisplayClass20_0.<AfterTestRunEnd>b__0() in /_/src/Microsoft.TestPlatform.CrossPlatEngine/DataCollection/ProxyDataCollectionManager.cs:line 155
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.DataCollection.ProxyDataCollectionManager.InvokeDataCollectionServiceAction(Action action, ITestMessageEventHandler runEventsHandler) in /_/src/Microsoft.TestPlatform.CrossPlatEngine/DataCollection/ProxyDataCollectionManager.cs:line 288
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 288
I'm not sure what is trying to be written/connected when the issue happens
The text was updated successfully, but these errors were encountered:
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.
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: