Skip to content

[#379] Fix stdout/stderr supression#380

Merged
Sereja313 merged 1 commit into
masterfrom
heitor-lassarote/#379-fix-exit-status-commands
Jun 9, 2026
Merged

[#379] Fix stdout/stderr supression#380
Sereja313 merged 1 commit into
masterfrom
heitor-lassarote/#379-fix-exit-status-commands

Conversation

@heitor-lassarote

@heitor-lassarote heitor-lassarote commented Jun 9, 2026

Copy link
Copy Markdown
Member

Fixes #379.

This PR restores the old semantics regarding child process handling and stdout/stderr modes. In #310, we were too eager to use output on processes rather than spawn where needed, causing the stdout/stderr to appear "hanged" rather than directly printed.

See the commit messages for more details.

Problem: With PR #310, we changed some semantics regarding how stdout
and stderr and handled. What we did was to get the output only after the
process has exited, rather than directly piping it. This is because some
commands used `spawn` rather than `output`, and we changed everything to
`output`.

Solution: Revert back to the old semantics. Whenever we had `status`
rather than `output`, we use `status` again. I also add a new command
error representing the exit status.

I also noticed that some commands used `wait` rather than
`wait_with_output`. I think using the latter should be innofensive, but
I am unsure whether this could break something or not, so I prefer to be
safe and revert to the old semantics.

I noticed that we also format exit statuses by only formatting their
exit codes. Well, we get nicer formatting if we format the exit status
itself, so I changed it so it's prettier and more informative (now we
see if we exited because of a signal).
@Sereja313 Sereja313 merged commit 2ce9051 into master Jun 9, 2026
10 checks passed
@Sereja313 Sereja313 deleted the heitor-lassarote/#379-fix-exit-status-commands branch June 9, 2026 16:48
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.

command hangs on "🚀 ℹ️ [deploy] [INFO] Running checks for flake in ."

2 participants