MC-4976 — [watchdog:failed:memory-extractor:2026-06-11 13] Task failed: memory-extractor (timeout)

Home Board MC-4976

[watchdog:failed:memory-extractor:2026-06-11 13] Task failed: memory-extractor (timeout)

Task `memory-extractor` finished with status **timeout** at 2026-06-11 13:01:36. Error (if captured): ``` Stale lock killed after 1874s ``` This may be a one-off or a recurrin...

State Done Next Action Closed Owner Luci Runtime Closed Age 2d ago

Description

MC-4976

Task `memory-extractor` finished with status **timeout** at 2026-06-11 13:01:36. Error (if captured): ``` Stale lock killed after 1874s ``` This may be a one-off or a recurring issue — check previous runs in mc.db `task_runs` table.

Activity

done

Luci is working...

Details — Done · High · Luci ▼

State

Done

Closed

State

Priority

People

Owner (assigned to)

Controller

Timing / Details

Due Date

Snooze

Source scheduler-watchdog (scheduled)

Project infra

Created 2d ago

Updated 2d ago

Advanced / Operator evidence

Routing owner

Routes via

Operator console

Evidence

Ticket is done; runtime is closed. MC is visibility-only. Hermes Luci launches and gates work outside MC, then mirrors evidence/status here.

Workflow

Start Dev Review + QA ▾

Select phases to include:

Research (scott) Implement (larry) (required) Council Review (council) Code Review (luci) Validate (tessa) (required) Sign-off (atlas)

Agents

Review Gates

Decision

WAT routing: choose an agent, review gate, or decision. Buttons use the live runtime when one is attached.

system 2d ago

[visibility-only] Queued message recorded for Hermes Luci. MC did not claim the ticket or spawn a runtime.

luci-board-manager 2d ago

[visibility-only controller] Routed this Luci-owned scheduler-timeout incident to internal Kanban card `t_75689ed9` on board `mc-internal` (assignee=codexbuilder) in isolated worktree `/home/lucienne/workspace/_mc_internal_worktrees/MC-4975-4976-scheduler-timeouts/workspace`. Scope covers the shared stale-lock timeout pattern for MC-4975/MC-4976; MC remains a dumb ledger and no MC runtime/pickup/send/harvest endpoint was used. Dispatch evidence: task status `running`, run `276`, pid `2057672`, cwd `/home/lucienne/workspace/_mc_internal_worktrees/MC-4975-4976-scheduler-timeouts/workspace`. Waiting on the Kanban review-required handoff.

luci-board-manager 2d ago

[visibility-only controller] Consumed internal Kanban parent `t_75689ed9` after its review-required implementation handoff (commit `9656e2a73dec4bda160127c31221cc995d70b99e`) and routed the bounded review/landing/verification lane to `t_b165a5ec` on board `mc-internal` in isolated workspace `/home/lucienne/workspace/_mc_internal_worktrees/MC-4975-4976-scheduler-timeouts/workspace`. Dispatch verification: task status `running`, run `279`, pid `2067902`, cwd `/home/lucienne/workspace/_mc_internal_worktrees/MC-4975-4976-scheduler-timeouts/workspace`. MC remains ledger-only; no MC pickup/runtime/send/harvest endpoint was used.

luci-board-manager 2d ago

[visibility-only controller gate] Verified and closed the scheduler stale-lock fix. Evidence: fix commit `9656e2a73dec4bda160127c31221cc995d70b99e` is contained in `/home/lucienne/workspace` `master` and `origin/master` (current HEAD/origin `b7d4ceb2fb54d2da8aacf48bdff3b60758dc0355`); `python3 -m pytest tests/test_scheduler_regressions.py::SchedulerBackgroundLockOwnershipTests -q` => `3 passed in 0.11s`; `python3 -m py_compile scheduler.py tests/test_scheduler_regressions.py` passed; `git diff --check HEAD~1..HEAD` passed; affected locks `/tmp/luci-task-life-manager-scan.lock`, `/tmp/luci-task-memory-extractor.lock`, and `/tmp/luci-task-memory-extractor-iris.lock` are absent. No MC pickup/runtime/send/harvest endpoint was used.