-
Notifications
You must be signed in to change notification settings - Fork 4.5k
[BEAM-10975] Remove capture_output argument in sdk_container_builder #12942
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
Conversation
Codecov Report
@@ Coverage Diff @@
## master #12942 +/- ##
=======================================
Coverage 82.31% 82.31%
=======================================
Files 455 455
Lines 54603 54603
=======================================
+ Hits 44945 44948 +3
+ Misses 9658 9655 -3
Continue to review full report at Codecov.
|
| _LOGGER.info("Building sdk container, this may take a few minutes...") | ||
| now = time.time() | ||
| subprocess.run(['docker', 'build', '.', '-t', container_image_name], | ||
| capture_output=True, |
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.
How about
subprocess.run([ ], stdout=subprocess.PIPE)
Woud this capture stdout and print STDERR?
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.
If there is an build error, how will users see it?
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.
Not capturing any output should help. But may be noisy. We can consider to capture the output but print it only if something goes wrong.
Leaving the change as is SGMT for now.
Please add a meaningful description for your change here
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username).[BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replaceBEAM-XXXwith the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
Post-Commit Tests Status (on master branch)
Pre-Commit Tests Status (on master branch)
See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI.