c90383dd07
Run 9 died the same way at t=486s, and the watcher's sampler had been running throughout: at the kill the cgroup held 6.5 GB of its 7.0 GB limit, the host had 12 GB free, and oom_kill was 0. So the memory-pressure suspicion recorded earlier is refuted - three kills, no OOM record on any, and the one with a full trace shows headroom on both the cgroup and the host. Also checked and clean: no stray process of mine was running, and the kills do not fall on a clock (08:31, 09:00, 09:14 - gaps of ~29 and ~14 minutes). Recorded as a container-level blocker rather than chased further, because nothing in here can attribute a SIGKILL to its sender: no dmesg, no audit, and ptrace_scope=1 limits strace to my own descendants. The practical response is to stop designing experiments that need a long run - the counter transitions the OB work needs all happen in the first minutes of flight. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PMRJjbxLqZtsb5Vb7KunPE