search for: _r_check_timings_

Hello: What is the recommended procedure for skipping long tests in "R CMD check --as-cran"? Some time ago, after a discussion on this list, I added the following function to the fda package: CRAN <- function (x = "_R_CHECK_TIMINGS_") { x. <- Sys.getenv(x) nchar(as.character(x.)) > 0 } However, it does not seem to be working with R 3.0.1. I know this, because the time to compute the examples in findFn.Rd in the sos package did not drop after I wrapped all the examples in the following: if(!CR...

Hello, All: The fda package has tests that run too long for CRAN's current rules. I'd like to wrap some examples in a construct like the following: if(!CRAN()){ ... } I tried the following: CRAN <- function(x='_R_CHECK_CRAN_INCOMING_'){ x. <- Sys.getenv(x) xl <- as.logical(x.) notCRAN <- is.na(xl) || xl # return(!notCRAN) }

...t;test all"? Footnote: the manual page for R CMD check (?check) has the line "Many of the checks in R CMD check can be turned off or on by environment variables: see Chapter 6 of the ?R Internals? manual". The reference should be chapter 7. That chapter does document the use of _R_CHECK_TIMINGS_=10. But it seems dangerous to use this as an indirect test, ie. "if timings is 10 then this must be CRAN running". My biggest time offender is in the vignettes. After multiple readings of the docs I still can't quite figure out how to specify - pdf files that should be in the...

I'm having a very hard time making R CMD check produce a clean check on examples because of the timings inserted into examples by R CMD check. I am getting a difference on every example output caused by timing information being inserted by 'R CMD check'. The current 'Writing R Extensions' manual[1] states on p. 14: If directory tests has a subdirectory Examples

.... o Where multiple sub-architectures are to be tested, R CMD check now runs the examples and tests for all the sub-architectures even if one fails. o R CMD check can optionally report timings on various parts of the check: this is controlled by environment variable _R_CHECK_TIMINGS_ documented in 'Writing R Extensions'. Timings (in the style of R CMD BATCH) are given at the foot of the output files from running each test and the R code in each vignette. o There are new options for more rigorous testing by R CMD check selected by environment vari...

.... o Where multiple sub-architectures are to be tested, R CMD check now runs the examples and tests for all the sub-architectures even if one fails. o R CMD check can optionally report timings on various parts of the check: this is controlled by environment variable _R_CHECK_TIMINGS_ documented in 'Writing R Extensions'. Timings (in the style of R CMD BATCH) are given at the foot of the output files from running each test and the R code in each vignette. o There are new options for more rigorous testing by R CMD check selected by environment vari...

...ge .Rd files, warning about invalid email addresses and (some) invalid URIs and noting empty \item labels in description lists. * R CMD check now also reports problems when reading package news in md (file NEWS.md) and (optionally) plain text (file NEWS) formats. * _R_CHECK_TIMINGS_ defaults to a value from the environment even for R CMD check --as-cran; this allows for exceptionally fast or slow platforms. It now applies to checking PDF and HTML versions of the manuals, and 'checking CRAN incoming feasibility'. * R CMD check can optionall...

...ge .Rd files, warning about invalid email addresses and (some) invalid URIs and noting empty \item labels in description lists. * R CMD check now also reports problems when reading package news in md (file NEWS.md) and (optionally) plain text (file NEWS) formats. * _R_CHECK_TIMINGS_ defaults to a value from the environment even for R CMD check --as-cran; this allows for exceptionally fast or slow platforms. It now applies to checking PDF and HTML versions of the manuals, and 'checking CRAN incoming feasibility'. * R CMD check can optionall...