On 21 May 2018 at 17:46, Uwe Ligges wrote: | In addition to what Dirk said, I just added this experimental test for | CRAN incoming checks few days ago and it should not reject but lead to | manual inspection, this will be fixed on CRAN side shortly. | | Nevertheless: The idea is that we have timeouts for checking a package | and we want to be alerted of future timeout problems in advance when a | package is submitted.
Which is totally understandable given the limits we have on (human, chiefly) resources here -- but it is also worth reminding ourselves from time to time that this of course reduces actual test coverage ... which is generally not we want with these tests. This whole topic needs some more discussion. On 21 May 2018 at 18:41, Chris Njuguna wrote: | Thank you for this! It makes a lot of sense. I will adopt this version | naming and testing scheme. Nice. I didn't give to much detail but if glance eg at https://github.com/RcppCore/Rcpp/blob/master/tests/doRUnit.R#L45-L52 for the detection (including an environment variable override) and eg at https://github.com/RcppCore/Rcpp/blob/master/inst/unitTests/runit.DataFrame.R#L21-L23 for one use case you should be able to get started. Ping me off-list with any questions. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
