Glue: allow multiple job runs #5483
Merged
Conversation
This file contains 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
bblommers
force-pushed
the
feature/glue-allow-multiple-job-runs
branch
2 times, most recently
from
e2723f1
to
fd55f51
Compare
bblommers
force-pushed
the
feature/glue-allow-multiple-job-runs
branch
from
fd55f51
to
bf853b5
Compare
Codecov Report
@@ Coverage Diff @@
## master #5483 +/- ##
=======================================
Coverage 96.10% 96.10%
=======================================
Files 724 724
Lines 72059 72070 +11
=======================================
+ Hits 69250 69263 +13
+ Misses 2809 2807 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
This is now part of moto >= 4.0.4.dev12 |
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.
See #5402
Also fixes the documentation to be inline with the actual implementation - the second argument for time-based progression should be
seconds, notdurationAlso fixes an import issue with S3, introduced in #5476