Merge release/8.0-staging into release/8.0 by steveisok · Pull Request #129250 · dotnet/runtime

steveisok · 2026-06-10T17:45:40Z

Merges release/8.0-staging into release/8.0.

This is a routine forward-merge of the staging branch into the release branch. The merge was performed with no conflicts.

Note

This pull request was generated with the assistance of GitHub Copilot.

) Manual backport of #106076 to release/8.0-staging ## Customer Impact - [x] Customer reported - [ ] Found internally #122057 Silent bad code caused by invalid loop invariant code motion. An error in tracking memory dependence can allow the JIT to hoist an expression that is not loop invariant out of a loop. While customer reported, the issue was found by Fuzzlyn. The known repro cases require a two-level loop nest, with an expression that is VN invariant (eg a constant) but memory dependent in the outerloop sitting below an inner loop. ## Regression - [ ] Yes - [X] No ## Testing Validated the repro case now passes. The issue was fixed in 9.0, though the fix had a slightly different form. ## Risk Low. This make the JIT more conservative about optimizing some constructs. No SPMI diffs for the 9.0 version of the fix; no SPMI diffs for libraries with the current fix. --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…126495) This pull request updates the following dependencies [marker]: <> (Begin:855db5a2-4d17-4346-a439-08dbcfd61a5a) ## From https://github.com/dotnet/runtime-assets - **Subscription**: [855db5a2-4d17-4346-a439-08dbcfd61a5a](https://maestro.dot.net/subscriptions?search=855db5a2-4d17-4346-a439-08dbcfd61a5a) - **Build**: [20260517.2](https://dev.azure.com/dnceng/internal/_build/results?buildId=2977343) ([314679](https://maestro.dot.net/channel/3073/github:dotnet:runtime-assets/build/314679)) - **Date Produced**: May 18, 2026 3:08:16 AM UTC - **Commit**: [d1fcc07ff6166c4aeb3d851e51bc824a1ee25eda](dotnet/runtime-assets@d1fcc07) - **Branch**: [release/8.0](https://github.com/dotnet/runtime-assets/tree/release/8.0) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - From [8.0.0-beta.26153.1 to 8.0.0-beta.26267.2][3] - Microsoft.DotNet.CilStrip.Sources - System.ComponentModel.TypeConverter.TestData - System.Data.Common.TestData - System.Drawing.Common.TestData - System.Formats.Tar.TestData - System.IO.Compression.TestData - System.IO.Packaging.TestData - System.Net.TestData - System.Private.Runtime.UnicodeData - System.Runtime.Numerics.TestData - System.Runtime.TimeZoneData - System.Security.Cryptography.X509Certificates.TestData - System.Text.RegularExpressions.TestData - System.Windows.Extensions.TestData [3]: dotnet/runtime-assets@5d4912b...d1fcc07 [DependencyUpdate]: <> (End) [marker]: <> (End:855db5a2-4d17-4346-a439-08dbcfd61a5a) --------- Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> Co-authored-by: Petr Onderka <petronderka@microsoft.com>

main PR #128775 # Description Backport of the WASI CI disable from 9.0-staging to 8.0-staging. `wasm-ld` from wasi-sdk dynamically links `libxml2.so.2`, renamed to `libxml2.so.16` in Ubuntu 26.04, breaking all WASI CI jobs. Contributes to #128772 - **`eng/pipelines/runtime.yml`**: Comment out WASI smoke tests and `simple-wasm-build-tests` - **`eng/pipelines/extra-platforms/runtime-extra-platforms-wasm.yml`**: Comment out WASI smoke tests, `simple-wasm-build-tests`, and optional WASI library tests # Customer Impact None. WASI CI is already broken; no runtime behavior changes. # Regression Yes — introduced by Ubuntu 26.04 image update (libxml2 soname change). # Testing CI-only change. Verified no uncommented `wasi`/`wasi_wasm` references remain in affected pipeline files. # Risk Low. Disabling CI jobs that are already failing. No production code touched. # Package authoring signed off? N/A — no package changes. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: maraf <10020471+maraf@users.noreply.github.com> Co-authored-by: pavelsavara <pavel.savara@gmail.com>

This makes the queues we use consistent everywhere.

This pull request updates the following dependencies [marker]: <> (Begin:f3ed209d-980c-4076-a437-08dbcfd61a5a) ## From https://github.com/dotnet/arcade - **Subscription**: [f3ed209d-980c-4076-a437-08dbcfd61a5a](https://maestro.dot.net/subscriptions?search=f3ed209d-980c-4076-a437-08dbcfd61a5a) - **Build**: [20260528.3](https://dev.azure.com/dnceng/internal/_build/results?buildId=2986525) ([316242](https://maestro.dot.net/channel/3885/github:dotnet:arcade/build/316242)) - **Date Produced**: May 28, 2026 9:35:33 PM UTC - **Commit**: [4b95fb1a9307265eb75f62d4937be50e6786e94e](dotnet/arcade@4b95fb1) - **Branch**: [release/8.0](https://github.com/dotnet/arcade/tree/release/8.0) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - From [8.0.0-beta.26224.3 to 8.0.0-beta.26278.3][1] - Microsoft.DotNet.Arcade.Sdk - Microsoft.DotNet.Build.Tasks.Archives - Microsoft.DotNet.Build.Tasks.Feed - Microsoft.DotNet.Build.Tasks.Installers - Microsoft.DotNet.Build.Tasks.Packaging - Microsoft.DotNet.Build.Tasks.TargetFramework - Microsoft.DotNet.Build.Tasks.Templating - Microsoft.DotNet.Build.Tasks.Workloads - Microsoft.DotNet.CodeAnalysis - Microsoft.DotNet.GenAPI - Microsoft.DotNet.GenFacades - Microsoft.DotNet.Helix.Sdk - Microsoft.DotNet.PackageTesting - Microsoft.DotNet.RemoteExecutor - Microsoft.DotNet.SharedFramework.Sdk - Microsoft.DotNet.VersionTools.Tasks - Microsoft.DotNet.XUnitExtensions - From [2.5.1-beta.26224.3 to 2.5.1-beta.26278.3][1] - Microsoft.DotNet.XUnitConsoleRunner [1]: dotnet/arcade@d9af20b...4b95fb1 [DependencyUpdate]: <> (End) [marker]: <> (End:f3ed209d-980c-4076-a437-08dbcfd61a5a) Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

…128933) This pull request updates the following dependencies [marker]: <> (Begin:855db5a2-4d17-4346-a439-08dbcfd61a5a) ## From https://github.com/dotnet/runtime-assets - **Subscription**: [855db5a2-4d17-4346-a439-08dbcfd61a5a](https://maestro.dot.net/subscriptions?search=855db5a2-4d17-4346-a439-08dbcfd61a5a) - **Build**: [20260602.3](https://dev.azure.com/dnceng/internal/_build/results?buildId=2989998) ([316810](https://maestro.dot.net/channel/3073/github:dotnet:runtime-assets/build/316810)) - **Date Produced**: June 2, 2026 10:03:14 AM UTC - **Commit**: [96ec5190831f0b214f15b3a7b6aab8b8b565d820](dotnet/runtime-assets@96ec519) - **Branch**: [release/8.0](https://github.com/dotnet/runtime-assets/tree/release/8.0) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - From [8.0.0-beta.26267.2 to 8.0.0-beta.26302.3][1] - Microsoft.DotNet.CilStrip.Sources - System.ComponentModel.TypeConverter.TestData - System.Data.Common.TestData - System.Drawing.Common.TestData - System.Formats.Tar.TestData - System.IO.Compression.TestData - System.IO.Packaging.TestData - System.Net.TestData - System.Private.Runtime.UnicodeData - System.Runtime.Numerics.TestData - System.Runtime.TimeZoneData - System.Security.Cryptography.X509Certificates.TestData - System.Text.RegularExpressions.TestData - System.Windows.Extensions.TestData [1]: dotnet/runtime-assets@d1fcc07...96ec519 [DependencyUpdate]: <> (End) [marker]: <> (End:855db5a2-4d17-4346-a439-08dbcfd61a5a) Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

@jeffhandley

…128579) Backport of #120546 to release/8.0-staging /cc @jeffhandley @tarekgh ## Customer Impact - [ ] Customer reported - [x] Found internally This test failed in CI on 9.0: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1431345&view=ms.vss-test-web.build-test-results-tab&runId=39820274&paneView=debug&resultId=132492. Since the same test exists on 8.0, I think it should be fixed there as well. ## Regression - [ ] Yes - [x] No ## Testing Verified in main, and the failing test is occurring in release/9.0-staging as well. ## Risk Low. Test only, handling new data. --------- Co-authored-by: Tarek Mahmoud Sayed <10833894+tarekgh@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Copilot

Pull request overview

Routine forward-merge from release/8.0-staging into release/8.0 bringing in a JIT loop-hoisting fix plus associated regression coverage and a set of test / infrastructure updates for the release branch.

Changes:

Fix optRecordLoopMemoryDependence to walk the update loop’s parent chain so memory dependencies are attributed to an ancestor loop when appropriate.
Add a new JIT regression test (Runtime_122057) that forces FullOpts (TieredCompilation=0) to validate the loop-hoisting scenario.
Update Arcade/runtime-assets dependency versions and adjust CI configuration (WASI/WASM jobs disabled; Helix macOS queues moved to OSX.15; tweak test skips).

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/tests/JIT/Regression/JitBlue/Runtime_122057/Runtime_122057.csproj	Adds new JIT regression test project with process isolation and TieredCompilation=0.
src/tests/JIT/Regression/JitBlue/Runtime_122057/Runtime_122057.cs	Adds the regression repro + checksum harness and xUnit entrypoint (note: contains a compile error as written).
src/libraries/System.Net.Sockets/tests/FunctionalTests/SendTo.cs	Broadens ActiveIssue scope to cover macOS + MacCatalyst for the failing test.
src/libraries/System.Globalization/tests/NumberFormatInfo/NumberFormatInfoNumberGroupSizes.cs	Makes the group-size assertion tolerant of an alternate expected pattern and improves failure diagnostics.
src/coreclr/jit/optimizer.cpp	Fixes loop-memory dependence tracking by walking parent loops to find an ancestor that encloses the consuming loop.
global.json	Updates MSBuild SDK versions (Arcade/Helix/SharedFramework).
eng/Versions.props	Updates Arcade and runtime-assets dependency versions.
eng/Version.Details.xml	Updates toolset dependency versions and SHAs to match Arcade/runtime-assets changes.
eng/pipelines/runtime.yml	Disables WASI/WASM templates (tracked by linked issue).
eng/pipelines/libraries/helix-queues-setup.yml	Moves macOS Helix queues from OSX.14 to OSX.15.
eng/pipelines/extra-platforms/runtime-extra-platforms-wasm.yml	Disables WASI templates in extra-platforms wasm pipeline (tracked by linked issue).
eng/pipelines/coreclr/templates/helix-queues-setup.yml	Moves coreclr Helix macOS queues from OSX.14 to OSX.15 (public + internal).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

) 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: * hoyosjs ## 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. <img alt="merge button instructions" src="https://i.imgur.com/GepcNJV.png" width="300" /> 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. ``` sh 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 ``` <details> <summary>or if you are using SSH</summary> ``` git push git@github.com:dotnet/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` </details> After PR checks are complete push the branch ``` git push ``` ## Instructions for resolving conflicts :warning: If there are merge conflicts, you will need to resolve them manually before merging. You can do this [using GitHub][resolve-github] or using the [command line][resolve-cli]. [resolve-github]: https://help.github.com/articles/resolving-a-merge-conflict-on-github/ [resolve-cli]: https://help.github.com/articles/resolving-a-merge-conflict-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 ``` <details> <summary>or if you are using SSH</summary> ``` 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 ``` </details> 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.

…e/release/8.0-staging-to-release/8.0

svick · 2026-06-15T20:35:58Z

/ba-g Failures are #129439, timeouts, deadletter or known

AndyAyersMS and others added 8 commits May 20, 2026 14:43

[release/8.0] Bump to OSX.15 helix queues (#128896)

efafc86

This makes the queues we use consistent everywhere.

Merge release/8.0-staging into release/8.0

efce61f

steveisok requested a review from radical as a code owner June 10, 2026 17:45

Copilot AI review requested due to automatic review settings June 10, 2026 17:45

Copilot started reviewing on behalf of steveisok June 10, 2026 17:45 View session

github-actions Bot added the area-codeflow for labeling automated codeflow label Jun 10, 2026

Copilot AI reviewed Jun 10, 2026

View reviewed changes

Comment thread src/tests/JIT/Regression/JitBlue/Runtime_122057/Runtime_122057.cs

svick added 2 commits June 15, 2026 15:55

Merge remote-tracking branch 'upstream/release/8.0-staging' into merg…

f09037b

…e/release/8.0-staging-to-release/8.0

svick added NO-SQUASH The PR should not be squashed Servicing-approved Approved for servicing release labels Jun 15, 2026

svick approved these changes Jun 15, 2026

View reviewed changes

svick mentioned this pull request Jun 15, 2026

Segmentation fault in System.Net.Http.Functional.Tests on macOS on 8.0 #129439

Open

svick merged commit 44cbf8d into release/8.0 Jun 15, 2026
190 of 203 checks passed

svick deleted the merge/release/8.0-staging-to-release/8.0 branch June 15, 2026 20:38

This was referenced Jun 15, 2026

slow macOS - "##[error]The job running on agent Azure Pipelines 9 ran longer than the maximum time of 60 minutes." dotnet/dnceng#1883

Open

[8.0] Failed to find a suitable device for target tvos-device #125522

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Merge release/8.0-staging into release/8.0#129250

Merge release/8.0-staging into release/8.0#129250
svick merged 10 commits into
release/8.0from
merge/release/8.0-staging-to-release/8.0

steveisok commented Jun 10, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

svick commented Jun 15, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Conversation

steveisok commented Jun 10, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

svick commented Jun 15, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants