Bump Microsoft.NET.Test.Sdk from 17.5.0-preview-20221003-04 to 17.5.0

[dependabot]

Bumps Microsoft.NET.Test.Sdk from 17.5.0-preview-20221003-04 to 17.5.0.

Release notes

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

v17.5.0

See the release notes here.

v17.5.0-preview-20221221-03

See the release notes here.

Changelog

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

17.5.0

Issues Fixed

• Fix SDK issue #4278
• Add test run serialization feature #4126
• Ensure that the OnAbort message is sent if the testhost aborts early #3993
• Add custom satellite assemblies resolution #4133
• Fixed muxer resolution strategy enum #4134
• Fixed dotnet resolution for in-process vstest.console scenarios #4122
• Ensure to not produce and ship exe for netcore #4124
• Fixed testhost crash for net7 #4112
• Revert "Run tests with Server GC enabled & concurrent GC disabled. (#3661)" #4108
• Revert making Microsoft.NET.Test.Sdk package transitive #4104
• Fix recursive resource lookup #4095
• Fixed CC for in-process console scenarios #4084
• Fixed test session issues #4075
• Fix Invalid target architecture 'S390x' error #4066
• Add Mono.Cecil.Rocks #4071
• Revert "Revert "Re-enable arm64 ngen (#3931)" (#3948)" #3951
• Update docker to the latest tagging schema #4041
• Update resources #4063
• Use environment variables for AeDebugger mode #4049
• Add postmortem blame mode #4032
• Add VSTEST_DISABLE_THREADPOOL_SIZE_INCREASE feature flag #4046

See full log here

Artifacts

• TestPlatform vsix: 17.5.0
• Microsoft.TestPlatform.ObjectModel: 17.5.0

17.5.0-preview-20221221-03

Issues Fixed

• Add test run serialization feature #4126
• Ensure that the OnAbort message is sent if the testhost aborts early #3993
• Add custom satellite assemblies resolution #4133
• Fixed muxer resolution strategy enum #4134
• Fixed dotnet resolution for in-process vstest.console scenarios #4122
• Ensure to not produce and ship exe for netcore #4124
• Fixed testhost crash for net7 #4112
• Revert "Run tests with Server GC enabled & concurrent GC disabled. (#3661)" #4108
• Revert making Microsoft.NET.Test.Sdk package transitive #4104
• Fix recursive resource lookup #4095
• Fixed CC for in-process console scenarios #4084
• Fixed test session issues #4075
• Fix Invalid target architecture 'S390x' error #4066

... (truncated)

Commits

• c1ee51a Cherry-pick "Remove chutzpah (#4249)" (#4282)
• e0cf151 Fix SDK issue (#4278)
• ca77858 Revert "Fix string conversion of `Microsoft.TestPlatform.Extensions.TrxLogger...
• 6b7b112 Fix string conversion of `Microsoft.TestPlatform.Extensions.TrxLogger.ObjectM...
• be79eb4 [rel/17.5] Update dependencies from devdiv/DevDiv/vs-code-coverage (#4214)
• f50b9ea Update dependencies from https://dev.azure.com/devdiv/DevDiv/_git/vs-code-cov...
• 73b521d Fix release notes script to allow -release (#4206)
• d7b6672 Update dependencies from https://dev.azure.com/devdiv/DevDiv/_git/vs-code-cov...
• 8067f03 Update dependencies from https://dev.azure.com/devdiv/DevDiv/_git/vs-code-cov...
• 54ea9f7 [main] Update dependencies from dotnet/arcade (#4191)
• 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:
.props : +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.

[dependabot]

Superseded by #40.