test(restart-chaos): list every sandbox process in the Runner probe

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
DottaandClaude committed 2026-11-10 20:51:51 -06:00
1 parent 4bb4b7dd33
commit f279b75564
2 files changed
+3 -3

No files matched your search

+1 -1
View File
@@ -367,7 +367,7 @@ minutes. In staging class R, recovery then found the remote Runner gone
with an `index.json`, and to `runner_logs_captured` in the timeline.
`daytona-runner-logs.ts` runs one fixed, read-only probe through the Daytona
toolbox. It reads:
- the Runner and provider processes (`ps`);
- every process (`ps`), so a running tool shows as a child of the Runner;
- memory, disk, and OOM lines from `dmesg`;
- the tail of every `runnerd.stderr.log`, `runner-process.identity` and
`runner-state.json`.
+2 -2
View File
@@ -20,8 +20,8 @@ import { redactKnownSecrets } from "./evidence.js";
export const RUNNER_LOG_PROBE = [
'echo "== observed_at $(date -u +%Y-%m-%dT%H:%M:%SZ)"',
'echo "== uptime"; cat /proc/uptime 2>/dev/null',
'echo "== runner and provider processes"; ps -eo pid,ppid,sid,etimes,stat,rss,args 2>/dev/null'
+ ' | grep -E "paperclip-runner|runnerd|opencode|codex|claude|acpx" | grep -v grep | cut -c1-400',
// Every process, not only the Runner's: a tool the agent started (for example T1's loop) shows as a child.
'echo "== processes"; ps -eo pid,ppid,sid,etimes,stat,rss,args 2>/dev/null | cut -c1-400 | head -n 120',
'echo "== memory"; free -m 2>/dev/null',
'echo "== disk"; df -h / /tmp 2>/dev/null',
'echo "== oom"; dmesg 2>/dev/null | grep -iE "oom|killed process" | tail -n 20',