Skip to content

fix(executor): ModelOp OOM vocabulary + planner-audit issues #369-#371#47

Merged
PaulFidika merged 1 commit into
masterfrom
planner-audit
Jul 4, 2026
Merged

fix(executor): ModelOp OOM vocabulary + planner-audit issues #369-#371#47
PaulFidika merged 1 commit into
masterfrom
planner-audit

Conversation

@PaulFidika

Copy link
Copy Markdown
Contributor

Gen-worker half of the planner audit (hub half: tensorhub PR #70, docs/planner.md + issues #533-#537).

  • Fix: ModelOp LOAD/UNLOAD failures always said load_failed, so the orchestrator's OOM reaction (handleModelFailure → UNLOAD a resident model for headroom) could never fire. OOM exceptions now emit ModelEvent{FAILED, error:"oom"} per contract §9. Unit tests included.
  • Issues filed in agents/progress.md (next_id → 372):
    • #369 residency registry must own the executor's pipelines — honest per-ref vram_bytes, serialized loads, multi-GPU probes
    • #370 keep-set disk retention — keep is write-only today, no disk GC exists (contract §7 unimplemented)
    • #371 worker-side VRAM juggling — make_room before load; UNLOAD demotes to the warm RAM tier instead of destroying the instance

uv run --extra dev pytest -q: 182 passed, 1 skipped.

🤖 Generated with Claude Code

…ct §9); file planner-audit issues #369-#371

The hub's OOM reaction (handleModelFailure -> UNLOAD a resident model for
headroom) was dead code: the worker emitted "load_failed" for every
LOAD/UNLOAD failure. Classify CUDA OOM into the contract vocabulary.

Issues #369 (residency owns executor pipelines / honest vram_bytes),
#370 (keep-set disk GC), #371 (worker-side VRAM juggling) filed in
agents/progress.md (next_id -> 372); hub counterparts tensorhub #533-#537,
design doc tensorhub docs/planner.md.
@PaulFidika PaulFidika merged commit 528c6ff into master Jul 4, 2026
1 check passed
@PaulFidika PaulFidika deleted the planner-audit branch July 4, 2026 07:38
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