Also test Thrust on SM120 in nightly/weekly CI

[bernhardmgruber]

I would love to also have it in the per pull request CI, but I guess @alliepiper tried to use the rtxpro6000 runners sparingly.

Fixes: #8877

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: fb7ec94c-7600-4eae-b581-f3206bba2527

📥 Commits

Reviewing files that changed from the base of the PR and between d98ac9d and 042d88d.

📒 Files selected for processing (1)

• ci/matrix.yaml

🚧 Files skipped from review as they are similar to previous changes (1)

• ci/matrix.yaml

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Expanded CI test coverage for RTX PRO 6000 hardware: nightly and weekly workflows now run additional project configurations (previously only one), increasing platform validation and overall test coverage for improved stability.

suggestion:

Walkthrough

CI matrix configuration expanded to run Thrust tests on RTX PRO 6000 (SM120) alongside CUB tests in both nightly and weekly workflows. The project field for RTX PRO 6000 coverage jobs changed from cub to ['cub', 'thrust'] at two matrix locations.

Changes

RTX PRO 6000 Thrust Coverage

Layer / File(s)	Summary
CI matrix Thrust expansion ci/matrix.yaml	Updated nightly and weekly workflow RTX PRO 6000 coverage matrix to test both CUB and Thrust projects instead of CUB only.

Assessment against linked issues

Objective	Addressed	Explanation
Add Thrust CI testing on SM120 [#8877]	✅

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

😬 CI Workflow Results

🟥 Finished in 1h 56m: Pass: 99%/501 | Total: 5d 20h | Max: 1h 47m | Hits: 74%/1007168

See results here.