[automated] Merge branch 'release/7.0-rc2' => 'release/7.0'

[dotnet-maestro-bot]

I detected changes in the release/7.0-rc2 branch which have not been merged yet to release/7.0. I'm a robot and am configured to help you automatically keep release/7.0 up to date, so I've opened this PR.

This PR merges commits made on release/7.0-rc2 by the following committers:

• github-actions[bot]

Instructions for merging from UI

This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.

If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.

Instructions for merging via command line

Run these commands to merge this pull request from the command line.

git fetch
git checkout release/7.0-rc2
git pull --ff-only
git checkout release/7.0
git pull --ff-only
git merge --no-ff release/7.0-rc2

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet-maestro-bot/runtime HEAD:merge/release/7.0-rc2-to-release/7.0

or if you are using SSH

git push [email protected]:dotnet-maestro-bot/runtime HEAD:merge/release/7.0-rc2-to-release/7.0

After PR checks are complete push the branch

git push

Instructions for resolving conflicts

⚠️ If there are merge conflicts, you will need to resolve them manually before merging. You can do this using GitHub or using the command line.

Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/7.0-rc2-to-release/7.0'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

git checkout -b merge/release/7.0-rc2-to-release/7.0 release/7.0
git pull https://github.com/dotnet-maestro-bot/runtime merge/release/7.0-rc2-to-release/7.0
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet-maestro-bot/runtime HEAD:merge/release/7.0-rc2-to-release/7.0

or if you are using SSH

git checkout -b merge/release/7.0-rc2-to-release/7.0 release/7.0
git pull [email protected]:dotnet-maestro-bot/runtime merge/release/7.0-rc2-to-release/7.0
(make changes)
git commit -m "Updated PR with my changes"
git push [email protected]:dotnet-maestro-bot/runtime HEAD:merge/release/7.0-rc2-to-release/7.0

Contact .NET Core Engineering if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[carlossanlop]

• The wasm JIT failures all look like the ones reported in: [release/7.0][wasm] Multiple JIT.* runtime test failures on rolling builds #75391
• Opened issue for the cryptography failure: CI failure: System.Security.Cryptography.X509Certificates.Tests.CertificateCreation.CertificateRequestLoadTests.VerifySignature_RSA_PSS(hashAlgorithm: "SHA512") #76099
• The tvOS failures in System.Net.Http.Json.Functional.Tests were false positives. All tests passed, yet the process reported it failed.

Some legs seem stuck, been running for days. I have to resolve the merge conflict, so the CI will have to restart anyway.

[carlossanlop]

CI failures are known and unrelated:

• OSX: Intermittent crash in DynamicGenerics test on OSX x64 #73299
• JIT: [release/7.0][wasm] Multiple JIT.* runtime test failures on rolling builds #75391
• Networking: CI failure in System.Net.Http.Functional.Tests - Operation timeout #75611