Get other.Rraw running again in r-devel#7833
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #7833 +/- ##
=======================================
Coverage 99.01% 99.01%
=======================================
Files 88 88
Lines 17234 17234
=======================================
Hits 17065 17065
Misses 169 169 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Generated via commit 20963c5 Download link for the artifact containing the test results: ↓ atime-results.zip
|
5dde771 to
58ce9c4
Compare
| @@ -1,9 +1,9 @@ | |||
| pkgs = c("DBI", "RSQLite", "bit64", "caret", "dplyr", "gdata", "ggplot2", "hexbin", "knitr", "nanotime", "nlme", "parallel", "plyr", "R.utils", "sf", "vctrs", "xts", "yaml", "zoo") | |||
| pkgs = c("DBI", "RSQLite", "bit64", "ggplot2", "caret", "dplyr", "gdata", "hexbin", "knitr", "nanotime", "nlme", "parallel", "plyr", "R.utils", "sf", "vctrs", "zoo", "xts", "yaml") | |||
There was a problem hiding this comment.
Could we maybe add a comment above why we enforce this ordering? seems out of the blue without reading later comment
There was a problem hiding this comment.
per the line below:
.gitlab-ci.yml uses parse(,n=1L) to read one expression from this file and installs pkgs.
(OTOH, that's not true, anymore at least)
There was a problem hiding this comment.
It is used here though:
| DT = data.table( a=1:5, b=11:50, d=c("A","B","C","D"), f=1:5, grp=1:5 ) | ||
| test(1.1, names(print(ggplot(DT,aes(b,f))+geom_point()))[c(1,3)], c("data","scales")) # update as described in #3047 | ||
| test(1.2, DT[,print(ggplot(.SD,aes(b,f))+geom_point()),by=list(grp%%2L)],data.table(grp=integer())) # %%2 to reduce time needed for ggplot2 to plot | ||
| print_without_error = function(x) !inherits(tryCatch(print(x), error=identity), "error") |
There was a problem hiding this comment.
Do we really need this here? Previously we/you have used the test(, {print(DT); TRUE}) idiom e.g. in test 2187
There was a problem hiding this comment.
Yea I was just finding it a bit cluttered here given how big the first expression before ; TRUE is.
Another option is to add a new test() argument to signify "not testing the output, just checking for errors/output". Maybe test(ignore_value = TRUE), WDYT?
There was a problem hiding this comment.
Yeah ignore_value=FALSe seems like the right way to got, while I personally find positive checks easier (personal taste) like check_value=TRUE

A few changes here:
attach.required=FALSEbut that's not present on R 3.5.0.print(<ggplot-obj>)works without error, so I refactored the tests to do that more directly.example()(described below).long double. I'm of half a mind to just delete that test because it's only testing {bit64} functionality anyway...test.data.table()if non-test code produces warnings #7210,warning()outside oftest()is caught, so change an intentional warning on Windows tocat().Without the update to
cedta()we get the telltalecedta()issues from here:data.table/inst/tests/other.Rraw
Lines 227 to 229 in fae95de
AIUI this is because of #7162 adding one more item on the call stack during execution of
example().Split off from #7832 as the actual debugging of package code should be done artisinally.