-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable coverage and docs #3096
Enable coverage and docs #3096
Conversation
Beware of 2.13.1 issue regarding scoverage/sbt-scoverage#295
Codecov Report
@@ Coverage Diff @@
## master #3096 +/- ##
==========================================
- Coverage 93.52% 93.17% -0.36%
==========================================
Files 368 372 +4
Lines 6998 7179 +181
Branches 198 207 +9
==========================================
+ Hits 6545 6689 +144
- Misses 453 490 +37
Continue to review full report at Codecov.
|
As of now on travis we only run coverage on Scala 2.12 using this job With this change we shall be able to delete this coverage dedicated job and run coverage for both 2.12 and 2.13 by changing the jvm tests job to do coverage as well. I.e. change the following
|
@kailuowang thanks for the remark, I forgot about travis. I'm reading the PR (#2737) that added the 2.12 coverage job, and there it states that running coverage reports for multiple scala versions is 'undefined'. So I'm not entirely sure if this is what we want to enable here. What are your thoughts? Also, regarding publishing API docs for 2.12 and 2.13 does anything need to change? I'm not familiar with microsite. In my projects I'm doing |
My thought was enabling coverage on both Scala versions makes some sense. True we will only get one codecov report, but I believe we have coverage threshold check, which fails the build if the delta coverage falls below (on the other hand I haven't seen that in action for a while, so maybe we need to check the settings, not necessarily in this PR though). For those coverage checks it kind of makes sense to have them on both Scala versions. Unfortunately our microsite is tied to only one Scala version. I propose we change it to Scala 2.13, although I am not 100% sure if sbt-microsite supports it yet. |
Ok that makes sense. Not sure what the correct place would be in the travis job though It seems that - &jvm_tests
stage: test
env: TEST="JVM tests"
script: sbt ++$TRAVIS_SCALA_VERSION! buildJVM bench/test
scala:
- *scala_version_212
- *scala_version_213 Where would coverage reporting then fit in |
that's good news. |
3911911
to
d247bf2
Compare
d247bf2
to
58f3d5f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Thanks for discovering the flag.
Just two nit comments
8e84291
to
3e4d184
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Fixed merge conflict with master. |
Addresses two points of #2347
Enable scoverage for 2.13 and enable scaladoc generation for 2.13.
One caveat with scoverage is that, for scala 2.13.1 (which Cats currently doesn't use), there are issues as described here scoverage/sbt-scoverage#295 and blocking an upgrade.
This might be decisive in dropping that commit from this PR, let me know.