Skip to content

fix(owner): observe natural exit before forced cleanup - #888

Merged
antropos17 merged 1 commit into
masterfrom
codex/installed-exit-observation-20261011
Oct 11, 2026
Merged

antropos17 merged 1 commit into
masterfrom
codex/installed-exit-observation-20261011

Conversation

@antropos17

Copy link
Copy Markdown
Owner

The hosted Windows qualification run 38130675459 reached the installed-owner baseline but recorded supervisorExitCode 259 and refused the expected original-program exit 2. The previous runtime sampled supervisor exit with a zero-time wait during cleanup, then terminated the Job. A native regression reproduced an EOF while the exact child was still active: the old runtime forced cleanup in 9 ms and reported the initial 259 even though the child would naturally exit 2.

The owner now waits only within the original deadline and a two-second cap for the retained supervisor to exit naturally before forced cleanup. It yields the cleanup gate between short polls so concurrent stop/expiry can still terminate promptly. An exit code is emitted only after the exact process handle signals; unknown is null. Expiry or native wait failure still runs mandatory Job cleanup.

The focused Windows native suite passed 8/8 cases, including delayed exit 2, genuine signaled 259, hung child, expired budget, and concurrent Dispose/Expire. ESLint, formatting and diff checks passed. Independent GPT-6.1 Sol review found no actionable P1/P2 findings. The exact hosted SYSTEM route, installed positive and VM remain unqualified; this PR does not claim acceptance.

@antropos17
antropos17 merged commit 985b451 into master Oct 11, 2026
5 checks passed
@antropos17
antropos17 deleted the codex/installed-exit-observation-20261011 branch October 11, 2026 10:27
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