Failed to negotiate protocol, waiting for response timed out after 90 seconds

[ificator]

Description

I followed these instructions to create a trivial project with some unit tests. The only deviation was that I added a global.json to use dotnet 2.2.300 instead of the 3.0 beta.

After having run through all the steps, dotnet test blocks for 90 seconds and then fails:

Test run for c:\temp\mstest\PrimeService.Tests\bin\Debug\netcoreapp2.2\PrimeService.Tests.dll(.NETCoreApp,Version=v2.2)
Microsoft (R) Test Execution Command Line Tool Version 16.1.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
Logging Vstest Diagnostics in file: c:\temp\mstest\PrimeService.Tests\log.txt
Failed to negotiate protocol, waiting for response timed out after 90 seconds. This may occur due to machine slowness, please set environment variable VSTEST_CONNECTION_TIMEOUT to increase timeout.

Test Run Aborted.

Steps to reproduce

1. Set up a test project as outlined in (https://docs.microsoft.com/en-us/dotnet/core/testing/unit-testing-with-mstest
2. Add a global.json for sdk version 2.2.300
3. Run dotnet test

Expected behavior

The tests run.

Actual behavior

The test execution blocks for 90 seconds then then fails. Logs suggest that System.Security.Permissions cannot be found.

Diagnostic logs

https://gist.github.com/ificator/ab9734c712e8e1be0df833d2a768a078

Environment

Windows 10 18362.239
Microsoft.NET.Test.Sdk 16.0.1 (also tried 16.2.0)
MSTest.TestAdapter" 1.4.0
MSTest.TestFramework 1.4.0
dotnet 2.2.300

[ificator]

I decided to go ahead and clear out my nuget cache for Microsoft.NET.Test.Sdk, MSTest.TestAdapter, and MSTest.TestFramework and that seems to have resolved things. No idea why though, unless somehow one of the packages was corrupt?