Can't run test in Azure with 17.6 latest VS test platform

[pshilpa1]

Description

Steps to reproduce

1. Azure Taskgroup is using latest stable VsTest installer
   
2. Run the test suite
3. It can't identify test scripts and can't run any automated test scripts and I had to cancel run after waiting for 30 mins

Expected behavior

Actual behavior

Can't identify tests and run is stuck until cancelled

Diagnostic logs

Working run with older version

Environment

[Evangelink]

Hi @pshilpa1,

Could you please let us know if you moved from 17.5 to 17.6 or if you did a bigger jump? Also, would it be possible to know what is the target framework of your test projects?

[pshilpa1]

We set it up in Azure to use latest stable so , 17.5 to 17.6
Target framework is .NET Framework4.8 for all test projects.

Thanks

[Evangelink]

If you try to run vstest.console.exe 17.6 locally, are you reproducing the issue or is it only reproducing through the vstest task on AzDo?

[pshilpa1]

Locally works fine , issue is only through Azure.

[jeromelaban]

nohwnd: Moved this to #4469.

---

I'm having a similar issue, and the build fails with the following trace running in Azure Devops hosted agents:

##[error]DiscoveryMessage : System.InvalidOperationException: The provided manager was not found in any slot.
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ParallelOperationManager`3.ClearCompletedSlot(TManager completedManager)
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ParallelOperationManager`3.RunNextWork(TManager completedManager)
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.Parallel.ParallelProxyDiscoveryManager.HandlePartialDiscoveryComplete(IProxyDiscoveryManager proxyDiscoveryManager, Int64 totalTests, IEnumerable`1 lastChunk, Boolean isAborted)
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.Parallel.ParallelDiscoveryEventsHandler.HandleDiscoveryComplete(DiscoveryCompleteEventArgs discoveryCompleteEventArgs, IEnumerable`1 lastChunk)
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyDiscoveryManager.InitializeDiscovery(DiscoveryCriteria discoveryCriteria, ITestDiscoveryEventsHandler2 eventHandler, Boolean skipDefaultAdapters)
   at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Client.ProxyDiscoveryManager.DiscoverTests(DiscoveryCriteria discoveryCriteria, ITestDiscoveryEventsHandler2 eventHandler)

The issue started when moving from 17.5 to 17.6 two days ago.

[nohwnd]

@pshilpa1 is that a distributed run?

[nohwnd]

I've tried multiple approaches but I can't repro. What is the configuration of your vstest task?

[nohwnd]

Ok can repro even locally now.

[nohwnd]

Workaround should be to make the dll selection narrower by changing the assembly filter to be specific to your test assembly names. Eg if all your tests are suffixed with UnitTests.dll or Tests.dll then you select just those from bin: #3939

[nohwnd]

I can also confirm this is working in 17.5

[nohwnd]

Merged into 17.6 and main. Insertion into dotnet/sdk 7.0.3xx that is shipping 17.6 is pending here: dotnet/sdk#32755.

[nohwnd]

#4516 workarounds summarized here.