Add a coverage report to pull requests #18
Draft
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
We've recently encountered two situations when testing the transform lambdas that should not raise errors. 1. someone manually creates a folder in a hub's raw/ S3 folder, which triggers an S3 creation event 2. model-output folders contain an .md or .txt file that should not be included in the transform process We still want the transform process to halt when one of the above scenarios occurs, but ideally raising a warning instead of an error will help eliminate this noise when querying Cloudwatch logs for errors.
bsweger
force-pushed
the
bsweger/add-coverage
branch
2 times, most recently
from
fc642c4 to
6abf3fa
Compare
bsweger
force-pushed
the
bsweger/add-coverage
branch
from
6abf3fa to
090f40b
Compare
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.
No description provided.