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
For a net core solution with tests, if a user performs a Build that triggers CBD discovery and performs a cancellation/rebuild when discovery is in progress, the discovery operation goes on for a considerably longer time and later reports that it could not find tests with the below stacktrace:
[7/13/2018 4:53:36 PM Informational] NUnit Adapter 3.8.0.0: Test discovery complete
[7/13/2018 4:55:04 PM Error] Microsoft.VisualStudio.TestPlatform.ObjectModel.TestPlatformException: Testhost process exited with error: The specified deps.json [D:\git\UnitTestVault\Generated\NUnit_10k.NetCore\bin\Debug\netcoreapp2.0\NUnit.NetCore.10k.Long.deps.json] does not exist
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.ThrowExceptionOnConnectionFailure(Int32 connTimeout)
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.SetupChannel(IEnumerable`1 sources)
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyDiscoveryManager.DiscoverTests(DiscoveryCriteria discoveryCriteria, ITestDiscoveryEventsHandler2 eventHandler)
[7/13/2018 4:55:05 PM Error] Microsoft.VisualStudio.TestPlatform.ObjectModel.TestPlatformException: Testhost process exited with error: The specified deps.json [D:\git\UnitTestVault\Generated\NUnit_10k.NetCore\bin\Debug\netcoreapp2.0\NUnit.NetCore.10k.Format1.deps.json] does not exist
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.ThrowExceptionOnConnectionFailure(Int32 connTimeout)
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.SetupChannel(IEnumerable`1 sources)
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyDiscoveryManager.DiscoverTests(DiscoveryCriteria discoveryCriteria, ITestDiscoveryEventsHandler2 eventHandler)
[7/13/2018 4:55:05 PM Error] Microsoft.VisualStudio.TestPlatform.ObjectModel.TestPlatformException: Testhost process exited with error: The specified deps.json [D:\git\UnitTestVault\Generated\NUnit_10k.NetCore\bin\Debug\netcoreapp2.0\NUnit.NetCore.10k.Format2.deps.json] does not exist
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.ThrowExceptionOnConnectionFailure(Int32 connTimeout)
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyOperationManager.SetupChannel(IEnumerable`1 sources)
at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyDiscoveryManager.DiscoverTests(DiscoveryCriteria discoveryCriteria, ITestDiscoveryEventsHandler2 eventHandler)
[7/13/2018 4:55:05 PM Informational] ========== Discover test finished: 0 found (0:01:33.7019648) ==========
This is more of a timing issue and is scoped mostly to process startup. It looks like it tries to start of another host process with the deps.json but since the clean operation would have cleared the deps.json by then the process fails to start. The connection logic however isn't aware of this failure and waits for connectiontimeout to be able to say it cannot connect to the process with the right message. If we could consider process launch failures while waiting we could potentially bail out sooner in these cases. NUnit.NetCore.10k.Double.zip
Do let me know if you need more information on this.
The text was updated successfully, but these errors were encountered:
Description
For a net core solution with tests, if a user performs a Build that triggers CBD discovery and performs a cancellation/rebuild when discovery is in progress, the discovery operation goes on for a considerably longer time and later reports that it could not find tests with the below stacktrace:
This is more of a timing issue and is scoped mostly to process startup. It looks like it tries to start of another host process with the deps.json but since the clean operation would have cleared the deps.json by then the process fails to start. The connection logic however isn't aware of this failure and waits for
connectiontimeout
to be able to say it cannot connect to the process with the right message. If we could consider process launch failures while waiting we could potentially bail out sooner in these cases.NUnit.NetCore.10k.Double.zip
Do let me know if you need more information on this.
The text was updated successfully, but these errors were encountered: