line-buffer stdout so progress is visible when output is redirected - #231
Merged
Merged
Conversation
GHC block-buffers stdout when it is not a terminal, so 'Checking behavior ...' progress lines are withheld until a block fills or the process exits. Piping an equiv run to a log therefore shows nothing for minutes to hours, and a healthy run looks identical to a hung one (this cost real debugging time on a multi-hour proof). Line buffering makes progress visible without changing any output.
anjapetkovic
approved these changes
Aug 7, 2026
anjapetkovic
left a comment
Collaborator
There was a problem hiding this comment.
Looks correct and helpful.
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.
GHC block-buffers stdout when it is not a terminal, so 'Checking behavior ...' progress lines are withheld until a block fills or the process exits. Piping an equiv run to a log therefore shows nothing for minutes to hours, and a healthy run looks identical to a hung one (this cost real debugging time on a multi-hour proof). Line buffering makes progress visible without changing any output.