-
Notifications
You must be signed in to change notification settings - Fork 37
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
V 0.3.1 to address CRAN testing issues #162
Conversation
Codecov Report
@@ Coverage Diff @@
## master #162 +/- ##
=======================================
Coverage 84.69% 84.69%
=======================================
Files 10 10
Lines 915 915
=======================================
Hits 775 775
Misses 140 140 Continue to review full report at Codecov.
|
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.
Makes sense to me! I'm sad we had to do this but CRAN has left us no choice
During testing, even though logs indicate the "on CRAN" route was taken, packages are still loaded. Seemingly, the setup and teardown testthat files are to blame even though they fall outside of the specified filter for tests on cran. By removing these files, we should see no issues on CRAN or R CMD check locally. However, |
Addresses #160.