-
Notifications
You must be signed in to change notification settings - Fork 47
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
Option for unbuffered stdout for cgreen-runner #312
Comments
Could you give an explicit example/test case of output where this would make a difference? If the debug output is also buffered would the output be different? Or perhaps you are thinking about timing, when debugging, e.g. stopping at a breakpoint when the output have been buffered but not flushed to the terminal yet? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When debugging complex tests that also output some additional debug info (custom state printouts, library debug output, etc.), it would be beneficial if the cgreen-runner process could configure its stdout as unbuffered (before forking into individual tests).
This could be done either via switch or environment variable.
The text was updated successfully, but these errors were encountered: