Modify .coveragerc to fix CI coverage #1204
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
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.
Motivation
code coverage CI is failing.
This PR attempts to fix that.
It seems there were two problems with the .coveragerc file:
coverage report, therun.omitsetting in.coveragercwas not being picked up. I moved the contents ofrun.omittoreport.omit.*tests*was not excluding the tests folder form coverage. I changed*tests*to `/tests/``.Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Verify coverage now succeeds on CI, and that coverage is still measured for the desired omegaconf source directory.