---
name: stopped-local-ssh-does-not-stop-its-remote-command
description: "TaskStop on a local ssh leaves the remote bash alive (no tty); relaunching the same chain then runs two full batteries concurrently in one pool and one output dir, forging load reds and a two-summary nextest.raw"
metadata: 
  node_type: memory
  type: project
  originSessionId: 6c1b8106-fa83-4fff-8e19-385f80067f8b
  modified: 2026-09-06T19:16:02.898Z
---

2026-09-06 18:24Z-18:50Z, kitsubito, W0 head 0b9554b3 (todlando's rig, my triage). He launched a
background `ssh kitsubito 'wait-for-old-driver → reset → driver → smoke'`, saw it would outlive
the local 10-min ssh cap, TaskStop'ped it, and relaunched the same chain detached with
`setsid nohup`. The stopped ssh's REMOTE bash did not die (no tty; it was sleeping in its wait
loop) — both chains woke when the old driver exited and ran TWO full `cargo nextest` suites over
ONE target dir and ONE `nextest.raw` (both opened `wb`, interleaved: one `Starting 2776 tests`
header, two `Summary` lines 1123 s / 1137 s, different fail sets and test numbering), two
smokes, one docs port. Load avg 15.3, `DOCS_SERVER_BIND_FAIL: 5474 in use`, and three
"load" reds (resident_service precondition ×2, ring_blocks, resume_no_control_steal) — every one
of them manufactured by the rig. The FIRST map I received named "load, exe-hash ready path" as
the mechanism and cited the 1-failed summary only; the second summary was 60 lines further down.

**Why:** a live-lane pool share (releases#103 class) reached through a process-lifetime gap
rather than through a path; nothing in the pool guard sees two nextests of the SAME lane. And
the driver's log grep (`sort -u | head -8`) showed one Summary, so the driver's own report
hid the second run.

**How to apply:** (1) never trust a nextest.raw with two `Summary` lines — `grep -c Summary`
before reading any FAIL line; two = void, not red. (2) A stopped local ssh is not a stopped
remote: kill by REMOTE pid, or make the remote side idempotent (lockfile per output dir — the
W0 driver now carries one). (3) A driver output dir is a pool: claim it. (4) When a red arrives
with a named LOAD mechanism, ask what ELSE was on the box before accepting — self-inflicted
load is a rig defect wearing a ledger row's name. See [[open-the-subindex-before-running-a-gate]]
and the pool rules in AGENTS.md.