Skip to content

[CI] Promote AMD and NVIDIA DirectX targets out of experimental#1187

Open
alsepkow wants to merge 5 commits into
llvm:mainfrom
alsepkow:promote-dx-targets
Open

[CI] Promote AMD and NVIDIA DirectX targets out of experimental#1187
alsepkow wants to merge 5 commits into
llvm:mainfrom
alsepkow:promote-dx-targets

Conversation

@alsepkow
Copy link
Copy Markdown
Contributor

@alsepkow alsepkow commented May 13, 2026

Both AMD and NVIDIA DirectX configurations have been stable and have higher pass rates than the existing Tier 1 Intel target. Promote them to Tier 1 so they run on every PR. Qualcomm and the Vulkan IHV configurations remain experimental and continue to require the test-all label.

Recent pass rates:

Target Passed
Intel 395 (81.44%)
Warp 423 (87.22%)
ARM64 Warp 422 (87.01%)
QC 375 (77.32%)
AMD 415 (85.57%)
Nvidia 414 (85.36%)

Changes

  • docs/CI.md: Promote Windows AMD GPU DirectX and Windows NVIDIA GPU DirectX from Experimental to Tier 1.
  • README.md: Move the AMD and NVIDIA DirectX rows from Experimental Targets to Tier 1 Targets in the status table.
  • .github/workflows/pr-matrix.yaml: Fold AMD and NVIDIA D3D12 (DXC + Clang) into the existing Exec-Tests-Windows job via include so they run on every PR. Narrow Exec-Tests-Extra (gated on test-all) to AMD/NVIDIA Vulkan + all QC targets.

Assisted by Claude Opus 4.7

Both AMD and NVIDIA DirectX configurations have been stable and have higher pass rates than the existing Tier 1 Intel target. Promote them to Tier 1 so they run on every PR. Qualcomm and the Vulkan IHV configurations remain experimental and continue to require the 'test-all' label.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@alsepkow alsepkow force-pushed the promote-dx-targets branch from af63cf9 to cab55cf Compare May 13, 2026 23:08
Match the tier change in docs/CI.md and pr-matrix.yaml so the README status table reflects that these targets now run on every PR.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@farzonl
Copy link
Copy Markdown
Member

farzonl commented May 13, 2026

Thank you Alex!

Copy link
Copy Markdown
Contributor

@bob80905 bob80905 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Comment thread .github/workflows/pr-matrix.yaml Outdated
matrix:
SKU: [windows-intel]
TestTarget: [check-hlsl-d3d12, check-hlsl-vk, check-hlsl-clang-d3d12, check-hlsl-clang-vk]
include:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit:
You might consider something like this:

matrix:
   SKU: [windows-intel, windows-amd, windows-nvidia]
   TestTarget: [check-hlsl-d3d12, check-hlsl-vk, check-hlsl-clang-d3d12, check-hlsl-clang-vk]
   exclude:
     - { SKU: windows-amd,    TestTarget: check-hlsl-vk }
     - { SKU: windows-amd,    TestTarget: check-hlsl-clang-vk }
     - { SKU: windows-nvidia, TestTarget: check-hlsl-vk }
     - { SKU: windows-nvidia, TestTarget: check-hlsl-clang-vk }

so that as future test targets get promoted, we can just remove exclusions, rather than needing to add specific inclusions. Something about this seems cleaner to me.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does seem cleaner to me assuming the expected state would eventually be that we don't have exclusions.

Per Bob's review feedback, switch from listing AMD/NVIDIA D3D12 combinations via 'include' to a cross-product with 'exclude' for the AMD/NVIDIA Vulkan combinations. As future targets get promoted out of experimental, we can simply remove exclusions rather than adding inclusions.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

@bob80905 bob80905 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bob approves 😋

alsepkow and others added 2 commits May 13, 2026 16:50
Apply the same cross-product + exclude pattern to the experimental Exec-Tests-Extra job for consistency. As targets are promoted out of experimental, exclusions can be added here in lockstep with their removal from the Tier 1 Exec-Tests-Windows job.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This reverts commit 1eec3eb.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants