Repository navigation
fix(cli): preserve non-zero exit code on stdout EPIPE #590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Lexiie
wants to merge
4
commits into
TestSprite:main
Choose a base branch
from
Lexiie:fix/489-epipe-preserve-exit-code
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
2c63e10
fix(create-batch): preserve per-spec creation failures in --run JSON …
4c5eb4c
fix(cli): preserve non-zero exit code on stdout EPIPE (#489)
8de9efa
chore: trigger CI entry check
7df483e
Merge remote-tracking branch 'upstream/main' into fix/489-epipe-prese…
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift
Resolve the final exit code before handling EPIPE.
Both paths read
process.exitCodebefore the top-level handler maps the command result.BrokenPipeInterruptErroris constructed while the exit code is still unset, so line 168 stores0. The armed path can therefore convert a failingtest wait,test run --wait, ortest rerun --waitinto success. The top-level handler readserr.exitCodebefore it assignsprocess.exitCode. (raw.githubusercontent.com)The disarmed path has the same ordering defect.
exit(0)can terminate the process before the final failure code is assigned.Pass the mapped command exit code into the broken-pipe path, or defer exit-code resolution until after command handling. Add regression tests for armed and disarmed EPIPE with an initially unset
process.exitCodeand a final code of1.As per path instructions, failed waits must preserve their documented non-zero exit code.
Also applies to: 369-369
🤖 Prompt for AI Agents
Source: Path instructions