-
Notifications
You must be signed in to change notification settings - Fork 21
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
Issue 486: Fix NOTEs for CRAN submission #514
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #514 +/- ##
=======================================
Coverage 90.92% 90.92%
=======================================
Files 23 23
Lines 1399 1399
=======================================
Hits 1272 1272
Misses 127 127 ☔ View full report in Codecov by Sentry. |
R/summarise_scores.R
Outdated
@@ -279,6 +279,7 @@ check_summary_params <- function(scores, | |||
#' summary is present according to the value specified in `by`. | |||
#' @examples | |||
#' library(magrittr) # pipe operator | |||
#' data.table::setDTthreads(1) # only needed to avoid issues on CRAN |
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.
why not using the same core count and dontshow everywhere?
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.
Nearly.
- Setting cores to 2 is not what is recommended in that thread but will work and makes sense.
- Can we be consistent with setting the number of cores and if we show that to users
- Suggest update the comment to be a bit more neutral
this was the recommendation that I used: Rdatatable/data.table#5658 (comment)
You're right, I updated the code |
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.
LGTM
🎉 |
Description
This PR closes #486
During CRAN submission, we got a Note on one of CRAN's machines that CPU time > elapsed time for some examples, tests, and the vignette- this is usually the case when more than 2 cores are used. We had that issue in the past and is almost certainly linked to
data.table
(see Rdatatable/data.table#3300 and Rdatatable/data.table#5658).To "solve" this I added the line
data.table::setDTthreads(2)
before offending code. This is what was suggested in Rdatatable/data.table#5658 by thedata.table
maintainers.(The PR also makes a single unrelated linting fix in the vignette)
Checklist
I have added or updated unit tests where necessary.I have updated the documentation if required.lintr::lint_package()
to check for style issues introduced by my changes.I have added a news item linked to this PR.