Bump Microsoft.NET.Test.Sdk from 17.6.0 to 17.6.1

[dependabot]

Bumps Microsoft.NET.Test.Sdk from 17.6.0 to 17.6.1.

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

v17.6.1

Issues Fixed

This is a tiny patch to fixup few latest issues,

• Fix no-suitable provider found by @​nohwnd in microsoft/vstest#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 microsoft/vstest#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 microsoft/vstest#4500 which fixes #4409

Internal updates:

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

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

Artifacts

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

Changelog

Sourced from Microsoft.NET.Test.Sdk's changelog.

17.6.1 and newer

Please see release notes directly in the release page: https://github.com/microsoft/vstest/releases

Commits

• 5121d9f [rel/17.6] Update Nuget.Frameworks (#4500)
• 00967c5 [rel/17.6] Fix hangdump running into crashdump (#4480)
• 90efc14 Disable internal build on new pipeline (#4476)
• 0e34e21 Merge branch 'rel/17.6' of https://github.com/microsoft/vstest into rel/17.6
• 1db7dc0 Bump to 17.6.1 in targets
• 7f3dc22 [rel/17.6] Update dependencies from devdiv/DevDiv/vs-code-coverage (#4479)
• a6e34a1 Revert "Bump Microsoft.VisualStudio.Telemetry to 16.6.13"
• 6115490 Bump Microsoft.VisualStudio.Telemetry to 16.6.13
• 68649f2 Re-order sources to restore signed packages
• 0d079b4 Update branding to 17.6.1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.csproj : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[ghost]

🎉v7.4.0-preview.4 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes