Fix no-suitable provider found - #4475
Merged
Jakub Jareš (nohwnd) merged 2 commits intoMay 23, 2023
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Add fixes that were not correctly merged in 17.6 in PR. This will pass only runnable sources (sources that have some test runtime provider) to the proxy execution/discovery manager, so when it tries to execute the source (and instantiate a new runtime provider for it) it will succeed rather than fail to resolve the provider.
https://github.com/microsoft/vstest/pull/3666/files#diff-1a8bafa7d283356b53d249b58c8c118f9e811003c7ddfa8e906a8fc4de1bef27L102-L112.
Related issue
Fix #4467