Merge release/dev16.8 to master

[dotnet-bot]

This is an automatically generated pull request from release/dev16.8 into master.

Once all conflicts are resolved and all the tests pass, you are free to merge the pull request. 🐯

Troubleshooting conflicts

Identify authors of changes which introduced merge conflicts

Scroll to the bottom, then for each file containing conflicts copy its path into the following searches:

• https://github.com/dotnet/roslyn/find/release/dev16.8
• https://github.com/dotnet/roslyn/find/master

Usually the most recent change to a file between the two branches is considered to have introduced the conflicts, but sometimes it will be necessary to look for the conflicting lines and check the blame in each branch. Generally the author whose change introduced the conflicts should pull down this PR, fix the conflicts locally, then push up a commit resolving the conflicts.

Resolve merge conflicts using your local repo

Sometimes merge conflicts may be present on GitHub but merging locally will work without conflicts. This is due to differences between the merge algorithm used in local git versus the one used by GitHub.

git fetch --all
git checkout merges/release/dev16.8-to-master
git reset --hard upstream/master
git merge upstream/release/dev16.8
# Fix merge conflicts
git commit
git push upstream merges/release/dev16.8-to-master --force

[ghost]

Hello @dotnet-bot!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

Do note that I've been instructed to only help merge pull requests of this repository that have been opened for at least 12 minutes. No worries though, I will be back when the time is right! 😉

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

[ghost]

Auto-approval

[RikkiGibson]

@jasonmalinowski @AlekseyTs It appears there is a determinism failure involving Microsoft.CodeAnalysis.EditorFeatures2.UnitTests.dll: https://dev.azure.com/dnceng/public/_build/results?buildId=888454&view=logs&jobId=057c83a9-93f9-5bce-4899-deb8d06fc190&j=057c83a9-93f9-5bce-4899-deb8d06fc190&t=483a0497-9f4d-53d7-5af2-784b067f0ccc

[jasonmalinowski]

#49402 was recently merged that removed the skip; is the bug still there or do we need to update a toolset somewhere?