Skip to content

Alternate half of linux arm64 CI runners from a100 to l4#1956

Merged
leofang merged 1 commit intoNVIDIA:mainfrom
leofang:arm64-l4-runners
Apr 21, 2026
Merged

Alternate half of linux arm64 CI runners from a100 to l4#1956
leofang merged 1 commit intoNVIDIA:mainfrom
leofang:arm64-l4-runners

Conversation

@leofang
Copy link
Copy Markdown
Member

@leofang leofang commented Apr 21, 2026

Change every other arm64 entry in the pull-request test matrix to use l4 GPU instead of a100, giving a 50/50 split (9 a100, 9 l4) in an alternating pattern. This reduces pressure on a100 runners while maintaining arm64 coverage across all Python and CUDA version combinations.

xref: https://github.com/nv-gha-runners/enterprise-runner-configuration/pull/311

Changes

  • 9 of 18 linux arm64 entries changed from a100 to l4 (every even-numbered row)
  • Updated copyright year (2025 → 2026) and header comment to reflect mixed GPU usage

Resulting arm64 matrix

# PY_VER CUDA_VER GPU
1 3.10 12.9.1 a100
2 3.10 13.0.2 l4
3 3.10 13.2.1 a100
4 3.11 12.9.1 l4
5 3.11 13.0.2 a100
6 3.11 13.2.1 l4
7 3.12 12.9.1 a100
8 3.12 13.0.2 l4
9 3.12 13.2.1 a100
10 3.13 12.9.1 l4
11 3.13 13.0.2 a100
12 3.13 13.2.1 l4
13 3.14 12.9.1 a100
14 3.14 13.0.2 l4
15 3.14 13.2.1 a100
16 3.14t 12.9.1 l4
17 3.14t 13.0.2 a100
18 3.14t 13.2.1 l4

-- Leo's bot

Change every other arm64 entry in the pull-request test matrix to use
l4 GPU instead of a100, giving a 50/50 split (9 a100, 9 l4) in an
alternating pattern. This reduces pressure on a100 runners while
maintaining arm64 coverage across all Python and CUDA version
combinations.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@copy-pr-bot
Copy link
Copy Markdown
Contributor

copy-pr-bot Bot commented Apr 21, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@leofang leofang self-assigned this Apr 21, 2026
@leofang leofang added the CI/CD CI/CD infrastructure label Apr 21, 2026
@leofang leofang added this to the cuda.core v1.0.0 milestone Apr 21, 2026
@leofang
Copy link
Copy Markdown
Member Author

leofang commented Apr 21, 2026

/ok to test 1a47e8b

@leofang leofang marked this pull request as ready for review April 21, 2026 13:37
leofang added a commit to leofang/numba-cuda that referenced this pull request Apr 21, 2026
Change every other arm64 entry in the pull-request test matrix to use
l4 GPU instead of a100, giving a ~50/50 split in an alternating
pattern (8 a100, 7 l4 active; plus 2 commented-out 3.14t entries
updated to match). This reduces pressure on a100 runners while
maintaining arm64 coverage across all Python and CUDA version
combinations.

Companion to NVIDIA/cuda-python#1956.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
leofang added a commit to leofang/numba-cuda that referenced this pull request Apr 21, 2026
Change every other arm64 entry in the pull-request test matrix to use
l4 GPU instead of a100, giving a ~50/50 split in an alternating
pattern (8 a100, 7 l4 active; plus 2 commented-out 3.14t entries
updated to match). This reduces pressure on a100 runners while
maintaining arm64 coverage across all Python and CUDA version
combinations.

Companion to NVIDIA/cuda-python#1956.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions

This comment has been minimized.

@leofang leofang enabled auto-merge (squash) April 21, 2026 14:28
@leofang leofang merged commit 46818dc into NVIDIA:main Apr 21, 2026
182 of 184 checks passed
@github-actions
Copy link
Copy Markdown

Doc Preview CI
Preview removed because the pull request was closed or merged.

@leofang leofang deleted the arm64-l4-runners branch April 21, 2026 15:36
@leofang
Copy link
Copy Markdown
Member Author

leofang commented Apr 21, 2026

Thanks, Phillip!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/CD CI/CD infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants