chore(deps): update dependency microsoft.net.test.sdk to v17.7.1

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
Microsoft.NET.Test.Sdk	nuget	minor	17.5.0 -> 17.7.1

---

Release Notes

microsoft/vstest (Microsoft.NET.Test.Sdk)

v17.7.1

What's Changed

• Take System dlls from testhost folder to fix running .NET Framework dlls on mono and under VS on Mac in #​4610 by @​Evangelink
• Fix hangs in parallel execution and discovery in #​4629 by @​nohwnd
• Fix executable bitness for testhost.x86 in #​4654 by @​nohwnd

Full Changelog: microsoft/vstest@v17.7.0...v17.7.1

v17.7.0

⚠️ Microsoft.TestPlatform 17.7.0 nuget package is hidden from Nuget.org, we've encountered an unexpected issue with versioning which prevents it from being used in all AzDO clients. We are working on a fix.

The most pressing issues were all backported to 17.6.1, 17.6.2 and 17.6.3.

Issues fixed (since 17.6.3)

• Don't print socket transport error in console by @​nohwnd in #​4493 which fixes #​4461
  When testhost crashes, we no longer print the transport error:

  ---> System.Exception: Unable to read data from the transport connection: 
  		An existing connection was forcibly closed by the remote host..
  

  This error is a side-effect or our architecture is almost never the culprit. Instead it leads developers away from the actual issue which is crash of testhost, or datacollector.

• Pass workloads to proxy managers in #​4422 by @​nohwnd
  Which allows datacollector users to only receive the sources that are currently running in the testhost associated to datacollector, instead of all the sources that have the same target framework.

• Fix Newtonsoft versions in testhost.deps.json in #​4367 by @​nohwnd
  testhost.runtimeconfig.json files that we ship with testhost contained an old version of Newtonsoft.Json. The version in this file does not have an effect on execution, but some compliance tools statically analyze it and report possible vulnerabilities.

Other fixes:

• Replacing calls to BuildMultipleAssemblyPath when passing only one source in acceptance tests in #​4358 by @​daveMueller
• Check for null Path in #​4391 by @​lewing
• Remove unused variable in #​4425 by @​mthalman
• Fix execution gets stucks on single netstandard source by @​nohwnd in #​4497 which fixes #​4392
• TestObject use ConcurrentDictionary instead of Dictionary in #​4450 by @​Evangelink
• Drop usage of Microsoft.Internal.TestPlatform.Remote in #​4456 by @​Evangelink

Special thanks to @​SimonCropp for the many fixes regarding nullability spelling and code style in #​4518, #​4520, #​4525, #​4526, #​4521, #​4519, #​4522, #​4529 🙇

Full Changelog: microsoft/vstest@v17.6.3...v17.7.0

Drops

• Microsoft.TestPlatform.ObjectModel : v17.7.0

v17.6.3

Issues Fixed

• [rel/17.6] Update version to 17.6.3 by @​nohwnd in #​4555
• [rel/17.6] Disable pre-start of testhosts by @​nohwnd in #​4554

Full Changelog: microsoft/vstest@v17.6.2...v17.6.3

Artifacts

• TestPlatform vsix: 17.6.3
• Microsoft.TestPlatform.ObjectModel : 17.6.3

v17.6.2

Fixes

This patch addresses the problems that were introduced in 17.6.0 that happen when running on AzDo with the default test.dll filter, which includes additional TestPlatform dlls into the run and fails it.

To mitigate this issue we solved the bug in 17.6.1, and added additional exclusions for known assemblies that are coming from TestPlatform and commonly used test adapters, to avoid trying to run tests from those assemblies.

Description and workarounds for this issue are available here: https://github.com/microsoft/vstest/issues/4516

• [rel/17.6] Downgrade Nuget.Frameworks to 6.5.0 by @​nohwnd in https://github.com/microsoft/vstest/pull/4512
• [rel/17.6] Filter out known platform sources by @​nohwnd in https://github.com/microsoft/vstest/pull/4517
• [rel/17.6] Exclude also known resource dlls by @​Evangelink in https://github.com/microsoft/vstest/pull/4528

Full Changelog: microsoft/vstest@v17.6.1...v17.6.2

Artifacts
TestPlatform vsix: 17.6.2
Microsoft.TestPlatform.ObjectModel : 17.6.2

v17.6.1

Issues Fixed

This is a tiny patch to fixup few latest issues,

• Fix no-suitable provider found by @​nohwnd in https://github.com/microsoft/vstest/pull/4474 which fixes #​4467

  When .NET Portable or .NET Standard dlls are provided to the run, the run crashes with "No suitable test runtime provider was found", which is a regression introduced in 17.6.0.
  

• Fix hangdump running into crashdump by @​nohwnd in https://github.com/microsoft/vstest/pull/4480 which fixes #​4378

  Running --blame-hang and --blame-crash at the same time, can result in --blame-hang cancelling --blame-crash, and killing the testhost in the process, resulting in no dumps being created. This fix waits for --blame-crash to finish dumping the process, and then it creates hang dump.

• Update Nuget.Frameworks by @​nohwnd in https://github.com/microsoft/vstest/pull/4500 which fixes #​4409

Internal updates:

• Update dependencies from devdiv/DevDiv/vs-code-coverage by @​dotnet-maestro in https://github.com/microsoft/vstest/pull/4479
• Disable internal build on new pipeline by @​nohwnd in https://github.com/microsoft/vstest/pull/4476

Full Changelog: microsoft/vstest@v17.6.0...v17.6.1

Artifacts

• TestPlatform vsix: 17.6.1
• Microsoft.TestPlatform.ObjectModel : 17.6.1

v17.6.0

See the release notes here.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.