Skip to content

GPU runners: no sm_89 label; a fallback card may be an A10G - #15

Merged
cbeck88 merged 1 commit into
mainfrom
gpu-any-label
Oct 19, 2026
Merged

cbeck88 merged 1 commit into
mainfrom
gpu-any-label

Conversation

@cbeck88-ai-dev

Copy link
Copy Markdown
Collaborator

The GPU runners' capacity ladder in aws-dev-infra is gaining g5 (A10G, sm_86) shapes. dps and snarkVM-cuda gpu-test already build CUDA_ARCH=sm_86 (upstream's arch, which runs on the L4 too) and already ask for [self-hosted, linux, x64, gpu], so the sm_89 label goes: a box retyped to g5 would carry it falsely.

  • start-runner.yml and README.md examples: runs-on: [self-hosted, linux, x64, gpu].
  • gpu-runner-preflight: the comment names the A10G as a possible fallback, and the off-card warning no longer says "different GPU memory" (an A10G has the same as an L4). New test: an A10G warns.

Needs v2 moved once merged. aws-dev-infra's test reads these docs, so this merges first.

🤖 Generated with Claude Code

The ladder can now retype a GPU box to a g5 (A10G, sm_86), and the CUDA
code under test builds sm_86, which runs on both. Callers ask for `gpu`
alone, and the preflight warning no longer claims a fallback card has
different memory.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@cbeck88
cbeck88 merged commit 9de02fc into main Oct 19, 2026
2 checks passed
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.

2 participants