Skip to content

Show GPU capacity before submission and explain allocation failures - #66

Merged
invi-bhagyesh merged 2 commits into
mainfrom
fix/explicit-gpu-capacity
Sep 24, 2026
Merged

invi-bhagyesh merged 2 commits into
mainfrom
fix/explicit-gpu-capacity

Conversation

@invi-bhagyesh

Copy link
Copy Markdown
Member

GPU stock was only checked on demand, and missing matching offers appeared as an unexplained unknown. The evaluation form now checks capacity automatically on entry and when GPU count or storage changes, refreshes every minute, and explains low/unavailable/unconfirmed stock before submission. It displays the backend's CUDA requirement and distinguishes capacity snapshots from reservations.

Allocation progress names the selected GPU and explains retries and that evaluation has not started. Exhausted capacity retries have a specific failure title. All selectable GPU IDs are covered by forwarding tests.

Validation: 96 backend tests passed, 5 skipped; TypeScript and production frontend build passed. CUDA 12.9 smoke requests covered all six GPU choices: three supply rejections, A100 PCIe/A40 allocated but upstream cu129 image failed on missing torchvision::nms, H100 allocated then stopped. All test pods terminated. Production CUDA and worker image are unchanged.

@invi-bhagyesh
invi-bhagyesh merged commit 94e8831 into main Sep 24, 2026
1 check passed
@invi-bhagyesh
invi-bhagyesh deleted the fix/explicit-gpu-capacity branch October 18, 2026 18:43
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