Cherry pick: Add back docker prune step between python container pushes (#28033)#28101
Merged
lostluck merged 1 commit intorelease-2.50.0from Aug 22, 2023
Merged
Cherry pick: Add back docker prune step between python container pushes (#28033)#28101lostluck merged 1 commit intorelease-2.50.0from
lostluck merged 1 commit intorelease-2.50.0from
Conversation
* Add back docker prune step between python container pushes * Extract to variables * Define var inside loop to avoid async race condition
Contributor
Author
|
R: @lostluck |
Contributor
|
Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control |
Codecov Report
@@ Coverage Diff @@
## release-2.50.0 #28101 +/- ##
==================================================
+ Coverage 70.84% 72.28% +1.43%
==================================================
Files 861 678 -183
Lines 105046 99676 -5370
==================================================
- Hits 74422 72051 -2371
+ Misses 29062 26065 -2997
+ Partials 1562 1560 -2
Flags with carried forward coverage won't be shown. Click here to find out more. see 203 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
lostluck
approved these changes
Aug 22, 2023
Contributor
Author
|
Run Python_Runners PreCommit |
Contributor
Author
|
Run Python_Integration PreCommit |
Contributor
Author
|
Run PythonDocs PreCommit |
Contributor
Author
|
Run Python_Integration PreCommit |
Contributor
|
Run PythonDocs PreCommit |
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.
Add back docker prune step between python container pushes
Extract to variables
Define var inside loop to avoid async race condition
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:
addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>instead.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.