GPU-001: GPU Detection and Allocation #195
Labels
No labels
blocked:children
blocked:commit-ready-failed
blocked:depends-231
blocked:depends-236
blocked:depends-237
blocked:depends-238
blocked:depends-239
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-research
blocked:needs-attention
blocked:needs-decision
blocked:no-changes
blocked:no-procedure
blocked:preflight
blocked:verify-failed
bug
enhancement
feature-request
high-priority
in-progress
lint-cleanup
needs-decompose
needs-triage
ops-retry
ops-task
phase-5
quickfix
security/medium
self-building
triage-approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Mark/mesh-seed#195
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
GSD RESEARCH phase failed: LLM provider timeout or error.
Retry on next pipeline tick.
Triage: decompose failed
Triage pipeline could not create a sub-issue for auto-decomposition (API error or repo permissions). Marking this
blocked:needs-decisionto prevent re-evaluation. Remove the label to retry.Fixup closure: deliverable already on master
GPU-001 (GPU Detection and Allocation) is implemented and verified on
origin/master:primitives/_bone/gpu_detector.py—detect_gpu()queries nvidia-smi (name, memory, driver, uuid) and returns device list/count. Present since commit16315ee(feat: Implement Phase 3.2 GPU Capability Routing, 2026-03-27, predates this issue).runtime/gpu_manager.py— GPUDevice/GPUNode/GPUManager with allocation helpers. Present since the Phase 0-4/Phase 3.2 implementation commits (2026-03-14 through 2026-03-31).39edeaf) and GPU monitoring (#197, commitf98427f), both closed.Verification:
pytest tests/unit/test_gpu_manager.py tests/unit/test_multi_gpu_routing.py tests/unit/test_gpu_monitor.py→ 56 passed.Why not --resume: this issue has no body/spec and no #195-specific plan or commit; the June salvage-state entry claims phases complete but produced no #195 commit (stale residue — the runner controller stalled at Review, same pattern as mesh-seed #78/#199). A live kilo-gsd run for #202 is in progress on the shared worktree; resuming #195 would collide with it. Closing with evidence instead.