Repository navigation
Fix macOS stdout-holder interruption test timing - #560
Merged
Merged
Conversation
This was referenced Oct 8, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix the false macOS failure by timing the stdout holder's stop before Failed run preservation and cleanup.
Closes #559
Evidence
cargo test --test process_tree interrupting_a_live_session_after_cli_exit_stops_the_command_holding_stdout -- --exact --nocapture(exit 101; 4.31 seconds).After: The same command passed while retaining the two-second holder-stop bound and verifying preserved work on origin.
cargo test --test process_treepassed.cargo check --all-targets,cargo fmt --check, andcargo clippy --all-targets -- -D warningspassed.cargo testpassed: 1503 tests passed, zero failed, 1 existing ignored test.Test seams
Review
Fixed point: GitHub's
issue-427atbdeac1e, pinned fromorigin/issue-427; the older local branch checked out in another worktree was left untouched.Standards: one P3 Duplicated Code judgement call, addressed by reusing
Scenario::repo_has_hook. Spec: no findings.Changed files left unread: Standards — none; Spec — none. Both reviewers read
tests/process_tree.rs, the only changed file.Unaddressed findings
Standards
None.
Spec
None.
Merge Danger
Door: two-way
Test-only change, reversible by reverting the commits.
Blast Radius: tests
The receive hook belongs to the test's temporary origin. CI jobs and production interruption behavior are unchanged.
Built with codex · gpt-6.1-sol · xhigh