remove coverage #3761
Merged
remove coverage #3761
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
rossabaker
previously approved these changes
Jan 31, 2021
larsrh
force-pushed
the
topic/kill-coverage
branch
from
89fc29b
to
d445864
Compare
mpilquist
approved these changes
Jan 31, 2021
|
Let the record reflect that @rossabaker approved, but I had to force-push 😉 |
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.
Completely rips out coverage from the Cats build.
Scoverage continues to be painful to support, see for example #3750. Furthermore, upstream hasn't released anything in quite a while, which blocks even Scala 2.12 and 2.13 support.
tl;dr coverage is not pulling its weight