[automated] Merge branch 'release/10.0.1xx' => 'release/10.0.2xx'

[github-actions]

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

This PR merges commits made on release/10.0.1xx by the following committers:

• SimonZhao888
• dotnet-maestro[bot]
• marcpopMSFT
• github-actions[bot]
• tmat
• Youssef1313
• nagilson
• dotnet-bot
• jjonescz
• joeloff
• MiYanni
• baronfel
• dsplaisted
• jkoritzinsky
• elinor-fung
• Copilot
• invalid-email-address
• mthalman

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/10.0.1xx
git pull --ff-only
git checkout release/10.0.2xx
git pull --ff-only
git merge --no-ff release/10.0.1xx

# 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/sdk HEAD:merge/release/10.0.1xx-to-release/10.0.2xx

or if you are using SSH

git push git@github.com:dotnet/sdk HEAD:merge/release/10.0.1xx-to-release/10.0.2xx

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/10.0.1xx-to-release/10.0.2xx'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.
The provided examples assume that the remote is named 'origin'. If you have a different remote name, please replace 'origin' with the name of your remote.

git fetch
git checkout -b merge/release/10.0.1xx-to-release/10.0.2xx origin/release/10.0.2xx
git pull https://github.com/dotnet/sdk merge/release/10.0.1xx-to-release/10.0.2xx
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet/sdk HEAD:merge/release/10.0.1xx-to-release/10.0.2xx

or if you are using SSH

git fetch
git checkout -b merge/release/10.0.1xx-to-release/10.0.2xx origin/release/10.0.2xx
git pull git@github.com:dotnet/sdk merge/release/10.0.1xx-to-release/10.0.2xx
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet/sdk HEAD:merge/release/10.0.1xx-to-release/10.0.2xx

Contact .NET Core Engineering (dotnet/dnceng) if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/main/.github/workflows/scripts/inter-branch-merge.ps1.

[SimonZhao888]

@nagilson could you please take a look at these failure test cases?

[nagilson]

This is all #51147

[nagilson]

I'm not sure why BA is not flagging all of them as known. It's 20 tests w/ the same issue. The string match pattern appears to be present in all of them. It worked for another PR (same case of tests and same failure cause) but not this one. I'll try to rerun the BA check.

[nagilson]

Ah, it manifests differently in the output as No template packages found matching in CanDisplayDetails_RemotePackage_NuGetFeedNoVersion. I'll try to make an issue tracker for that as well.

[nagilson]

So, I can't mark that as a known issue because the proper output is in stdout and it's not on helix so its not captured in the text to scan. The best I could do is flag DotnetNewDetailsTest.CanDisplayDetails_RemotePackage_NuGetFeedNoVersion.verified.txt\nCompare Result:\n11 Repository as a known issue but I'd need to do that for all of the tests. I think this might be the outlier test but I could be wrong, so I'll see if its only that one.

If not, then I'll just propose we merge this on red.

[nagilson]

@SimonZhao888 May you please help to mark all of these template engine tests as skipped and track that? I apologize that the known issue tracking isn't really sufficient in this case.

For reference:
Failed to update search cache. (The SSL connection could not be established, see inner exception.) is in the test failures such as Microsoft.DotNet.Cli.New.IntegrationTests.DotnetNewSearchTests.CanDisplayNoResults and it looks like it might be still categorized as a failure. I could be missing one of the 20 tests failure causes, but I checked all of them and think they all match the pattern.

[SimonZhao888]

May you please help to mark all of these template engine tests as skipped and track that? I apologize that the known issue tracking isn't really sufficient in this case.

OK, got it!