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

[github-actions]

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

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

• dotnet-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/9.0
git pull --ff-only
git checkout release/9.0-staging
git pull --ff-only
git merge --no-ff release/9.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/9.0-to-release/9.0-staging

or if you are using SSH

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

or if you are using SSH

git fetch
git checkout -b merge/release/9.0-to-release/9.0-staging origin/release/9.0-staging
git pull git@github.com:dotnet/runtime merge/release/9.0-to-release/9.0-staging
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet/runtime HEAD:merge/release/9.0-to-release/9.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.

[mrek-msft]

/azp run

[azure-pipelines]

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

[matouskozak]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[matouskozak]

@lewing was the update of LLVM intended for servicing branches? I see there is a tvOS crash which looks suspiciously related to LLVM change (bad instruction crash)

Coalition: net.dot.iOS.Device.ParallelForEachAsync.Test [767]
User ID: 501
Date/Time: 2026-07-09 15:13:34.6867 -0700
Launch Time: 2026-07-09 15:13:34.4689 -0700
Hardware Model: AppleTV5,3
OS Version: Apple TVOS 26.2 (23K54)
Release Type: User
Crash Reporter Key: fc3b1abb879409b4a61085885ac5d0a16ce52c8e
Incident Identifier: 5DA22B7E-EE8C-4D83-9C37-DD959A397334
Time Awake Since Boot: 170000 seconds
Triggered by Thread: 9 .NET TP Worker
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x00000000dac143e0
Termination Reason: Namespace SIGNAL, Code 4, Illegal instruction: 4
Terminating Process: exc handler [838]
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0:
0 libsystem_kernel.dylib 0x1b498e874 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x1b498f3e8 mach_msg2_internal + 72
2 libsystem_kernel.dylib 0x1b498f378 mach_msg_overwrite + 524
3 libsystem_kernel.dylib 0x1b498f160 mach_msg + 20
4 CoreFoundation 0x19310ec9c __CFRunLoopServiceMachPort + 156
5 CoreFoundation 0x19310f520 __CFRunLoopRun + 1180
6 CoreFoundation 0x193135438 _CFRunLoopRunSpecificWithOptions + 496
7 GraphicsServices 0x1d73beabc GSEventRunModal + 116
8 UIKitCore 0x19f9150c8 -[UIApplication _run] + 772
9 UIKitCore 0x19f919660 UIApplicationMain + 148
10 ...e.ParallelForEachAsync.Test 0x1004cc524 main + 68
11 dyld 0x191e6189c start + 2592
Thread 1:
Thread 2 name: Dispatch queue: com.apple.root.default-qos
Thread 2:
0 libsystem_kernel.dylib 0x1b498e8c8 swtch_pri + 8
1 libsystem_pthread.dylib 0x1b2ee4ef0 cthread_yield + 32
2 ...e.ParallelForEachAsync.Test 0x10052cb98 PalSwitchToThread() + 12
3 ...e.ParallelForEachAsync.Test 0x10055b60c S_P_CoreLib_System_Threading_Thread__Yield + 44
4 ...e.ParallelForEachAsync.Test 0x10055b6e4 S_P_CoreLib_System_Threading_Thread__StartCore + 132
5 ...e.ParallelForEachAsync.Test 0x10058bcd4 S_P_CoreLib_System_Threading_PortableThreadPool_GateThread__CreateGateThread + 148
6 ...e.ParallelForEachAsync.Test 0x10058bc00 S_P_CoreLib_System_Threading_PortableThreadPool_GateThread__EnsureRunningSlow + 48
7 ...e.ParallelForEachAsync.Test 0x100563560 S_P_CoreLib_System_Threading_ThreadPool__UnsafeQueueUserWorkItem_1 + 96
8 ...e.ParallelForEachAsync.Test 0x10059cd34 System_Threading_Tasks_Parallel_System_Threading_Tasks_Parallel_ForEachAsyncState_1<Int32>__QueueWorkerIfDopAvailable + 196
9 ...e.ParallelForEachAsync.Test 0x1005b5de0 System_Threading_Tasks_Parallel_System_Threading_Tasks_Parallel__ForEachAsync_2<Int32> + 208
10 ...e.ParallelForEachAsync.Test 0x100597fbc iOS_Device_ParallelForEachAsync_Test_Program__GitHubIssue_114262_Async_d__1__MoveNext + 316
11 ...e.ParallelForEachAsync.Test 0x1005bceb8 S_P_CoreLib_System_Runtime_CompilerServices_AsyncMethodBuilderCore__Start<iOS_Device_ParallelForEachAsync_Test_Program__GitHubIssue_114262_Async_d__1> + 72
12 ...e.ParallelForEachAsync.Test 0x100597d2c iOS_Device_ParallelForEachAsync_Test_Program__GitHubIssue_114262_Async + 44
13 ...e.ParallelForEachAsync.Test 0x100598158 iOS_Device_ParallelForEachAsync_Test_Program__Main_d__2__MoveNext + 120
14 ...e.ParallelForEachAsync.Test 0x1005bd0e8 S_P_CoreLib_System_Runtime_CompilerServices_AsyncMethodBuilderCore__Start<iOS_Device_ParallelForEachAsync_Test_Program__Main_d__2> + 72
15 ...e.ParallelForEachAsync.Test 0x100597d74 iOS_Device_ParallelForEachAsync_Test_Program__Main + 36
16 ...e.ParallelForEachAsync.Test 0x100597da0 iOS_Device_ParallelForEachAsync_Test_Program___Main_ + 16
17 ...e.ParallelForEachAsync.Test 0x1005a9490 __managed__Main + 80
18 ...e.ParallelForEachAsync.Test 0x1004cc2f8 __29-[ViewController viewDidLoad]_block_invoke + 52
19 libdispatch.dylib 0x1a82a177c _dispatch_call_block_and_release + 24
20 libdispatch.dylib 0x1a82b919c _dispatch_client_callout + 12
21 libdispatch.dylib 0x1a82d3924 _dispatch_queue_override_invoke.cold.3 + 28
22 libdispatch.dylib 0x1a82a5a90 _dispatch_queue_override_invoke + 772
23 libdispatch.dylib 0x1a82b1c48 _dispatch_root_queue_drain + 320
24 libdispatch.dylib 0x1a82b23e0 _dispatch_worker_thread2 + 184
25 libsystem_pthread.dylib 0x1b2edf988 _pthread_wqthread + 228
26 libsystem_pthread.dylib 0x1b2edf828 start_wqthread + 8

Since MAUI net9 is out of support, I suppose we don't need to worry too much about mobile builds but I wanted to check first.

[lewing]

the llvm change here is just tooling not the version bump from main dotnet/llvm-project@caaecce...3704f52

[matouskozak]

I've done more digging and found the failure on another run https://helixr1107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-heads-release-90-staging-f43d3990065b4e16a0/System.Runtime.Tests/1/console.4d21cf16.log?helixlogtype=result, so it's not caused by this PR, sorry for false positive.

[svick]

/ba-g all errors are timeouts or known

[svick]

@lewing@matouskozak Great, thanks for confirming.