[automated] Merge branch 'release/8.0' => 'release/8.0-staging'

[github-actions]

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

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

• dotnet-maestro[bot]
• tannergooding
• vseanreesermsft
• jozkee

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/8.0
git pull --ff-only
git checkout release/8.0-staging
git pull --ff-only
git merge --no-ff release/8.0

# 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/runtime HEAD:merge/release/8.0-to-release/8.0-staging

or if you are using SSH

git push git@github.com:dotnet/runtime HEAD:merge/release/8.0-to-release/8.0-staging

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/8.0-to-release/8.0-staging'. 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/8.0-to-release/8.0-staging origin/release/8.0-staging
git pull https://github.com/dotnet/runtime merge/release/8.0-to-release/8.0-staging
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet/runtime HEAD:merge/release/8.0-to-release/8.0-staging

or if you are using SSH

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

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.

[tannergooding]

looks like a large number of WASM tests are failing with an error similar to

error NU1301: Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/public/_packaging/darc-pub-dotnet-runtime-488a8a35/nuget/v3/index.json

CC. @akoeplinger

[akoeplinger]

Interesting. If I navigate to that URL I get this error from AzDO:

The feed 'darc-pub-dotnet-runtime-488a8a35' (91c80750-d8eb-4274-a088-aa6827c26cda) has been disabled."

[akoeplinger]

no idea where this reference is even coming from, it's not in nuget.config ...

[akoeplinger]

oh, interesting: dotnet/installer#20609 (comment)

[akoeplinger]

ok that one was unrelated, we do have it hardcoded as well in https://github.com/dotnet/runtime/blob/release/8.0-staging/src/mono/wasm/Wasm.Build.Tests/data/nuget8.config#L13-L16

[tannergooding]

We likely need the same change backported to release/8.0 since we're also seeing it in #119740 -- I had logged dotnet/dnceng#6180 to track the failure

[akoeplinger]

you mean we need it earlier than the next release/8.0-staging -> release/8.0 merge?

[tannergooding]

you mean we need it earlier than the next release/8.0-staging -> release/8.0 merge?

It depends on when that merge is. We have several other codeflow PRs waiting (for both 8.0 and 8.0-staging) and we shouldn't really assume that WASM is all correct given the entire leg is failing to run tests right now.