Skip to content
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

runner.docker: Avoid merging stdout and stderr together #155

Merged
merged 1 commit into from
Mar 4, 2022

Conversation

tsibley
Copy link
Member

@tsibley tsibley commented Mar 1, 2022

Further conditionalizes the use of --tty for docker run so that the
container process' stdout and stderr aren't merged when the user of
nextstrain wishes to redirect one or both of them elsewhere.

Resolves #152.

Testing

Tested with manual invocations in many permutations to ensure output remains separated. I wanted to write some Cram tests to prevent regressions, but this turns out to be difficult as Cram itself needs to redirect stdout/stderr of the test file's commands in order to do its own job. Maybe later I'll sort that out…

Further conditionalizes the use of --tty for `docker run` so that the
container process' stdout and stderr aren't merged when the user of
`nextstrain` wishes to redirect one or both of them elsewhere.

Resolves #152.
@tsibley tsibley requested a review from a team March 1, 2022 22:49
@tsibley tsibley merged commit 403cb83 into master Mar 4, 2022
@tsibley tsibley deleted the trs/fix-merged-stdout-stderr branch March 4, 2022 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

[docker] Docker runner sends stderr to stdout
2 participants