Skip to content

chore(deps): bump local CUDA 13.3 + R610 minimum driver (CI deferred)#62

Open
lusoris wants to merge 1 commit into
masterfrom
chore/bump-cuda-13.3-r610-20260528
Open

chore(deps): bump local CUDA 13.3 + R610 minimum driver (CI deferred)#62
lusoris wants to merge 1 commit into
masterfrom
chore/bump-cuda-13.3-r610-20260528

Conversation

@lusoris
Copy link
Copy Markdown
Contributor

@lusoris lusoris commented May 28, 2026

Summary

  • apt bump: cuda-toolkit-13-2cuda-toolkit-13-3 in dev/Containerfile. Package cuda-toolkit-13-3_13.3.0-1_amd64.deb confirmed present in NVIDIA ubuntu2404 apt repo (2026-05-28).
  • Min driver: R610.43.02 (Linux x86_64) documented in docs/backends/cuda/overview.md and docs/development/build-flags.md.
  • sm_103: Blackwell GB203 (RTX 5070/5060 Ti) added to gencode table in cuda/overview.md gated nvcc >= 13.3.
  • ADR-0738 filed; core/AGENTS.md invariant added (three-file update contract for future toolkit bumps).

Deferred (with reason)

Item Reason
CI Jimver pin cuda: '13.2.0''13.3.0' 13.3.0 absent from Jimver/cuda-toolkit src/links/linux-links.ts (verified 2026-05-28). Will break all CUDA CI legs if bumped now.
NVCR nvcr.io/nvidia/cuda base image No 13.3.x-devel-ubuntu24.04 tag on Docker Hub (verified via v2 API, count: 0).

Follow-up trigger: run gh api repos/Jimver/cuda-toolkit/contents/src/links/linux-links.ts | jq -r '.content' | base64 -d | grep 13.3 — when it returns a result, open a follow-up PR to bump the CI workflow pin and this ADR status note.

Smoke test

Container build smoke (local — skip if podman unavailable on agent):

podman build -f dev/Containerfile -t vmafx-cuda-13.3-smoke . 2>&1 | tail -20

Container build was skipped in this agent run (agent isolation rule: no docker exec). Run manually to verify cuda-toolkit-13-3 installs cleanly.

Six deep-dive deliverables

  • Research digest: no digest needed: routine version bump tracking NVIDIA GA
  • ADR ## Alternatives considered: bump everything blind (rejected — CI breaks), wait for Jimver (rejected — local users blocked), partial bump (chosen) — see ADR-0738
  • core/AGENTS.md invariant: R610.43.02 minimum driver + three-file update contract for CUDA toolkit bumps
  • Reproducer: podman build -f dev/Containerfile -t vmafx-cuda-13.3-smoke . 2>&1 | tail -20
  • changelog.d/changed/bump-cuda-13.3-r610-local.md fragment
  • docs/rebase-notes.md entry (three-file contract + Jimver lag note)

Docs updated (CLAUDE §12 r10)

  • docs/backends/cuda/overview.md: min driver section, sm_103 row, CUDA 13.3 notes section
  • docs/development/build-flags.md: enable_cuda row min driver note

State

  • docs/state.md: _Updated: row added for T-CUDA-133-R610-BUMP-2026-05-28

🤖 Generated with Claude Code

@lusoris lusoris marked this pull request as ready for review May 28, 2026 18:21
@lusoris lusoris enabled auto-merge (squash) May 28, 2026 18:21
…l Jimver+NVCR ship 13.3)

NVIDIA apt repo carries cuda-toolkit-13-3 (13.3.0-1) as of 2026-05-28; bump
the dev/Containerfile pin from 13-2 to 13-3. Document R610.43.02 as the new
minimum host driver for CUDA 13.3 runtime in cuda/overview.md and build-flags.md.
Add Blackwell sm_103 gencode row (GB203, nvcc >= 13.3). CI Jimver pin stays on
13.2.0 (13.3.0 absent from linux-links.ts); NVCR image tag also deferred (no
13.3.x-devel tag on Docker Hub). ADR-0738.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@lusoris lusoris force-pushed the chore/bump-cuda-13.3-r610-20260528 branch from f86a6c8 to 42a5835 Compare May 28, 2026 19:38
lusoris added a commit that referenced this pull request May 28, 2026
…ver)

PR #62 fixed the runtime segfault but missed the Containerfile directory
references left over from the ADR-0700 libvmaf/ → core/ rename. Fixes:
- COPY source path (libvmaf/ → core/)
- COPY destination path (/build/vmaf/libvmaf/ → /build/vmaf/core/)
- `cd libvmaf` in meson-setup RUN step
- `cd libvmaf` in ninja-install RUN step
- Three inline comments naming the old path (including core/src/meson.build)

Without this change `docker build` fails at the COPY layer because the
source directory `libvmaf/` no longer exists in the build context.
Manually patched during container rebuild on 2026-05-28; this commit
formalizes it.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.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.

1 participant