Bump Microsoft.TestPlatform.ObjectModel from 17.5.0 to 17.6.3

[dependabot]

Bumps Microsoft.TestPlatform.ObjectModel from 17.5.0 to 17.6.3.

Release notes

Sourced from Microsoft.TestPlatform.ObjectModel's releases.

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: microsoft/vstest#4516

• [rel/17.6] Downgrade Nuget.Frameworks to 6.5.0 by @​nohwnd in microsoft/vstest#4512
• [rel/17.6] Filter out known platform sources by @​nohwnd in microsoft/vstest#4517
• [rel/17.6] Exclude also known resource dlls by @​Evangelink in microsoft/vstest#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 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

... (truncated)

Changelog

Sourced from Microsoft.TestPlatform.ObjectModel's changelog.

Release Notes

17.6.1 and newer

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

17.6.0

Issues Fixed

• Add legacy feeds
• [rel/17.6] Fix Newtonsoft versions in testhost.deps.json #4372
• Revert "Revert "Fix signature verification" (#4333" #4345
• Revert "Fix signature verification" #4333
• Fix signature verification #4331
• Pre-start testhosts #3666
• Add dotnet vstest deprecation message #4297
• Catch unhandled exception and avoid crash on test host exit #4291
• Remove chutzpah #4249
• Fix string conversion of Microsoft.TestPlatform.Extensions.TrxLogger.ObjectMode.TestOutcome #4243
• Fix potential trx logger NRE #4240
• handle object disposed exception #4221
• Added support for checking testhost compatibility with test sessions #4199

See full log here

Artifacts

• TestPlatform vsix: 17.6.0
• Microsoft.TestPlatform.ObjectModel : 17.6.0

17.3.3

Issues Fixed

• [rel/17.3] Update Newtonsoft.Json to 13.0.1 #4299

See full log here

Drops

• TestPlatform vsix: 17.3.3
• Microsoft.TestPlatform.ObjectModel : 17.3.3

17.2.1

Issues Fixed

• [rel/17.2] Update Newtonsoft.Json to 13.0.1 #4310

See full log here

... (truncated)

Commits

• e7ea853 [rel/17.6] Update version to 17.6.3 (#4555)
• bda2d1e [rel/17.6] Disable pre-start of testhosts (#4554)
• 911a038 [rel/17.6] Exclude also known resource dlls (#4528)
• 4f929dd [rel/17.6] Filter out known platform sources (#4517)
• 3c283e0 [rel/17.6] Downgrade Nuget.Frameworks to 6.5.0 (#4512)
• 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
• 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)

[Xtansia]

Changelog in main needs tidying post 1.x release before merging

[Xtansia]

Changelog in main needs tidying post 1.x release before merging

[Xtansia]

@dependabot rebase

[opensearch-trigger-bot]

The backport to 1.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.x 1.x
# Navigate to the new working tree
cd .worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-271-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b3312fcfcdf33f102837a0a984b0f781ec5e4acb
# Push it to GitHub
git push --set-upstream origin backport/backport-271-to-1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.x

Then, create a pull request where the base branch is 1.x and the compare/head branch is backport/backport-271-to-1.x.