Skip to content

Kill watcher fixtures directly instead of via denied group signals - #154

Merged
w4ffl35 merged 1 commit into
masterfrom
fix/eval-watcher-fixture-kill
Oct 13, 2026
Merged

w4ffl35 merged 1 commit into
masterfrom
fix/eval-watcher-fixture-kill

Conversation

@w4ffl35

@w4ffl35 w4ffl35 commented Oct 13, 2026

Copy link
Copy Markdown
Member

Unblocks the RSI baseline gate: headlesscode-job fixture cleanup used bare group kill, denied (EPERM) in the eval sandbox, leaving sleep fixtures alive so the watcher correctly kept the job spawned. Direct child kill is equivalent for these single-process exec fixtures. Verified: host green; seccomp container denying negative-pid kill passes all 11 file tests. Fails in the fleet without this change (rsi-20261013123114 baseline).

The headlesscode-job tests cleaned up exec'd sleep fixtures with
process.kill(-pid), which is EPERM in the eval sandbox. The kill was
swallowed, the fixture survived, and the watcher (correctly, via
procfs) still saw a live group, failing the baseline gate. The
fixtures are single-process groups, so direct child kill is exactly
equivalent and policy-immune.
@w4ffl35
w4ffl35 merged commit e281dea into master Oct 13, 2026
2 checks passed
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