Update dependency Microsoft.NET.Test.Sdk to v17 #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
e81e3ad
to
e86dc2c
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
e86dc2c
to
1a9b89c
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
1a9b89c
to
a3e1177
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
a3e1177
to
89bb74a
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
2 times, most recently
from
a800ecc
to
acbbd4c
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
acbbd4c
to
e82a756
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
e82a756
to
89cb19f
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
89cb19f
to
991afeb
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
991afeb
to
80bed47
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
80bed47
to
f092bdb
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
f092bdb
to
4712723
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
4712723
to
a4704cc
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
a4704cc
to
a481fdd
Compare
renovate
bot
force-pushed
the
renovate/major-vstest-monorepo
branch
from
a481fdd
to
986bfcf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
15.7.0->17.10.0Release Notes
microsoft/vstest (Microsoft.NET.Test.Sdk)
v17.10.0What's Changed
2338548by @dotnet-bot in https://github.com/microsoft/vstest/pull/4794And many infrastructure related changes and updates.
New Contributors
Full Changelog: microsoft/vstest@v17.9.0...v17.10.0
v17.9.0What's Changed
HtmlLoggerby @daveMueller in https://github.com/microsoft/vstest/pull/4744New Contributors
Full Changelog: microsoft/vstest@v17.8.0...v17.9.0
v17.8.0What's Changed
Full Changelog: microsoft/vstest@v17.7.2...v17.8.0
v17.7.2What's Changed
Full Changelog: microsoft/vstest@v17.7.1...v17.7.2
v17.7.1What's Changed
Full Changelog: microsoft/vstest@v17.7.0...v17.7.1
v17.7.0The 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:
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:
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
v17.6.3Issues Fixed
Full Changelog: microsoft/vstest@v17.6.2...v17.6.3
Artifacts
v17.6.2Fixes
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
Full Changelog: microsoft/vstest@v17.6.1...v17.6.2
Artifacts
TestPlatform vsix: 17.6.2
Microsoft.TestPlatform.ObjectModel : 17.6.2
v17.6.1Issues 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:
Full Changelog: microsoft/vstest@v17.6.0...v17.6.1
Artifacts
v17.6.0See the release notes here.
v17.5.0See the release notes here.
v17.4.1See the release notes here.
v17.4.0See the release notes here.
v17.3.3See the release notes here.
v17.3.2See the release notes here.
v17.3.1See the release notes here.
v17.3.0See the release notes here.
v17.2.1See the release notes here.
v17.2.0See the release notes here.
v17.1.0See the release notes here.
v17.0.2See the release notes here.
v17.0.0See the release notes here.
v16.11.0See the release notes here.
v16.10.0See the release notes here.
v16.9.4See the release notes here.
v16.9.1See the release notes here.
v16.8.3See the release notes here.
v16.8.0See the release notes here.
v16.7.1See the release notes here
v16.7.0See the release notes here.
v16.6.1See the release notes here.
v16.6.0See the release notes here.
v16.5.0See the release notes here.
v16.4.0Release notes here
v16.3.0Release notes here
v16.2.0Release notes: here
v16.1.1Release Notes here
v16.0.1Release Notes here
v15.9.0: 15.9.0Release notes here
v15.8.0Release notes here.
v15.7.2Release 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.
This PR has been generated by Mend Renovate. View repository job log here.