Skip to content

Flaky test KillingLimit_TerminatesOverCapProcess makes CI on main red (child exits before the kill) - #762

Merged
AdamFrisby merged 1 commit into
mainfrom
codeybox/5e56b634
Nov 9, 2026
Merged

AdamFrisby merged 1 commit into
mainfrom
codeybox/5e56b634

Conversation

@AdamFrisby

Copy link
Copy Markdown
Owner

Automated via CodeyBox — work item 5e56b634952d44078b065ffdcf9e0865

Initiated by CodeyBox operator


Co-Authored-By: CodeyBox noreply@codeybox.invalid
🤖 Generated with CodeyBox

…erministic

Make termination by the output limit the only way the child process ends in
KillingLimit_TerminatesOverCapProcess by using an unbounded producer
('exec yes 0123456789abcdef') and a bounded CancellationToken safety net.
Assert StdoutLimitExceeded, !Success, and that the process terminated with a
non-zero exit code (SIGKILL exit code 137 on Linux).

Add a separate deterministic test
KillingLimit_CleanExitBeforeKill_ReportsSuccessWithLimitExceeded documenting
and asserting that if a process finishes and exits cleanly with code 0 before
the runner's limit-kill takes effect, the runner faithfully reports ExitCode = 0,
Success = true, and StdoutLimitExceeded = true with bounded stdout retention.

CodeyBox-Prompt-Revision: 1
Co-Authored-By: CodeyBox <noreply@codeybox.invalid>
@AdamFrisby
AdamFrisby merged commit 76ee55b into main Nov 9, 2026
@AdamFrisby
AdamFrisby deleted the codeybox/5e56b634 branch November 9, 2026 09:26
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