Since SDK 2.2.300 test performance is magnitudes slower

Description

Tests take a long time to run on detached hosts build servers (CircleCI)

Similar issue was closed, but the issue still happens. https://github.com/microsoft/vstest/issues/2078

Steps to reproduce

Repo which can reproduce the issue https://github.com/davidruhmann/vstest2080

Expected behavior

Tests to complete < 1s

Actual behavior

Tests take over > 20s

Each line of Test run in progress. output takes several seconds while the test takes < 2 ms.

Diagnostic logs

https://circleci.com/gh/davidruhmann/vstest2080/3

Environment

.NET Core SDK (reflecting any global.json):
 Version:   2.2.401
 Commit:    729b316c13

Runtime Environment:
 OS Name:     debian
 OS Version:  9
 OS Platform: Linux
 RID:         debian.9-x64
 Base Path:   /usr/share/dotnet/sdk/2.2.401/

Host (useful for support):
  Version: 2.2.6
  Commit:  7dac9b1b51

.NET Core SDKs installed:
  2.2.401 [/usr/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.2.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.2.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.2.6 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

[martincostello]

Can workaround the issue by specifying the following parameter to dotnet test:

'--logger:Console;noprogress=true'

[JSkimming]

@davidruhmann Try separating the package restore and build from the test steps. you’re doing all three in a single step that takes 27 seconds; I usually do something like the following:

dotnet restore
dotnet build --no-restore
dotnet test --no-restore --no-build

If you do this in distinct CirlceCI steps it will give you a more accurate reflection of where the time is being taken.