Split ARM64 integration tests by area

[andrewlock]

Summary of changes

Split the arm64 integration tests by area

Reason for change

These are starting to take a long time, we should probably split them out into their target areas. Costs more in agent numbers, but reduces overall runtime as long as we don't saturate, and reduces chance of flake by running fewer unnecessary tests.

Implementation details

Just start doing the split

Test coverage

This is the test

Other details

Stacked on

• Add [Trait("Area", "CiVisibility")] to CI Vis tests, and run in dedicated jobs only when required #9169

[andrewlock]

@codex review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-03T17:05:02.432498Z	8b22f0a	Manual request
🔒 Security Review	✅ Completed 2026-09-03T17:05:49.959438Z	8b22f0a	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: 8b22f0a526

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Security review completed. No security issues were found in this pull request.

Reviewed commit: 8b22f0a526

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

• You comment "@codex security review"
• A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

[dd-trace-dotnet-ci-bot]

Execution-Time Benchmarks Report ⏱️

Execution-time results for samples comparing This PR (9172) and master.

✅ No regressions detected

📄 View the full report (charts + all metrics) →