search for: donttest

Hi all, anyone has an idea how I could fix this? \donttest{ ## Set colors from colorspace package with a fallback col <- try(colorspace::rainbow_hcl(5), silent = TRUE) %||% rainbow(5) } The problem is that this makes R CMD check freak out (http://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/falsy-00check.html) if the colorspace pac...

On 08/12/2014 9:40 AM, G?bor Cs?rdi wrote: > Hi all, > > anyone has an idea how I could fix this? > > \donttest{ > ## Set colors from colorspace package with a fallback > col <- try(colorspace::rainbow_hcl(5), silent = TRUE) %||% rainbow(5) > } > > The problem is that this makes R CMD check freak out > (http://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-debian-clang/falsy-00chec...

On Mon, Dec 8, 2014 at 3:32 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: [...] > Why not declare colorspace as a "Suggests:" kind of dependency? I guess that is a solution. :/ In another example in the 'disposables' package I have: \donttest{ pkg <- make_packages( foo1 = { f <- function() print("hello!") ; d <- 1:10 }, foo2 = { f <- function() print("hello again!") ; d <- 11:20 } ) foo1::f() foo2::f() foo1::d foo2::d dispose_packages(pkg) } So in this case should I suggest '...

On Mon, Dec 8, 2014 at 3:43 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: [...] > In this case, I don't see a way to include that code but avoid warnings. So > you could ask for forgiveness when you submit it to CRAN (and perhaps they > would be forgiving), or you could use some other code in your example. Just to clarify, the code does not give any errors, or even

...nstance, I have examples which get data from the Internet. If I wrap them in try() then they can be skipped if the Internet is not available, but may not be tested in cases when I would like to know about the failure. (Not to mention that the example syntax is ugly.) If I mark them \dontrun or \donttest then they are not tested. I could mark them \dontrun and then use example() but for this, in addition to run.dontrun=TRUE, I would need to specify all topics for a package, and I don't see how to do this, missing topic does not work. Wishlist: what I would really like is R CMD check --run-d...

...get data from the > Internet. If I wrap them in try() then they can be skipped if the > Internet is not available, but may not be tested in cases when I would > like to know about the failure. (Not to mention that the example > syntax is ugly.) > > If I mark them \dontrun or \donttest then they are not tested. I could > mark them \dontrun and then use example() but for this, in addition to > run.dontrun=TRUE, I would need to specify all topics for a package, > and I don't see how to do this, missing topic does not work. > > Wishlist: what I would really lik...

...rom the Internet. >> If I wrap them in try() then they can be skipped if the Internet is not >> available, but may not be tested in cases when I would like to know >> about the failure. (Not to mention that the example syntax is ugly.) >> >> If I mark them \dontrun or \donttest then they are not tested. I could >> mark them \dontrun and then use example() but for this, in addition to >> run.dontrun=TRUE, I would need to specify all topics for a package, and >> I don't see how to do this, missing topic does not work. >> >> Wishlist: what I...

...y the same code* in my console with system.time(), I get user system elapsed 0.95 0.16 1.17 What could be the explanation for this? Second, the .log file from Win Builder shows only the *first example* with > 10s time. I have been able to reduce the time by wrapping part of the example in \donttest{}. I run Win Builder again, and the NOTE appears for another file. Very annoying. It would be far more helpful to see these all together, rather than having to do this incrementally. -Michael -- Michael Friendly Email: friendly AT yorku DOT ca Professor, Psychology Dept. & Chair, Quantitat...

Here?s a patch that adds ?seealso? entries to Sys.time and system.time docs, to help people who forget what the distinction is between them. Patch was made against https://svn.r-project.org/R/trunk at 61454 . -Ken

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) }

...l in future become the default for compiling C++. * The new built-in Rd macro \dontdiff{} can be used to mark example code whose output should be ignored when comparing check output to reference output (tests/Examples/<pkg>-Ex.Rout.save). The \dontdiff tag, like \donttest, is _not_ shown on the rendered help page, so provides a clean alternative to ## IGNORE_RDIFF_(BEGIN|END) comments. * R CMD build when there is no NAMESPACE, now uses the recommended exportPattern("^[^.]"), instead of exporting everything. * R CMD check now war...

...l in future become the default for compiling C++. * The new built-in Rd macro \dontdiff{} can be used to mark example code whose output should be ignored when comparing check output to reference output (tests/Examples/<pkg>-Ex.Rout.save). The \dontdiff tag, like \donttest, is _not_ shown on the rendered help page, so provides a clean alternative to ## IGNORE_RDIFF_(BEGIN|END) comments. * R CMD build when there is no NAMESPACE, now uses the recommended exportPattern("^[^.]"), instead of exporting everything. * R CMD check now war...

...TILITIES: * R --help now mentions the option --no-echo (renamed from --slave) and its previously undocumented short form -s. * R CMD check now optionally checks configure and cleanup scripts for non-Bourne-shell code ('bashisms'). * R CMD check --as-cran now runs \donttest examples (which are run by example()) instead of instructing the tester to do so. This can be temporarily circumvented during development by setting environment variable _R_CHECK_DONTTEST_EXAMPLES_ to a false value. PACKAGE INSTALLATION: * There is the beginnings of...

...TILITIES: * R --help now mentions the option --no-echo (renamed from --slave) and its previously undocumented short form -s. * R CMD check now optionally checks configure and cleanup scripts for non-Bourne-shell code ('bashisms'). * R CMD check --as-cran now runs \donttest examples (which are run by example()) instead of instructing the tester to do so. This can be temporarily circumvented during development by setting environment variable _R_CHECK_DONTTEST_EXAMPLES_ to a false value. PACKAGE INSTALLATION: * There is the beginnings of...

...TILITIES: * R --help now mentions the option --no-echo (renamed from --slave) and its previously undocumented short form -s. * R CMD check now optionally checks configure and cleanup scripts for non-Bourne-shell code ('bashisms'). * R CMD check --as-cran now runs \donttest examples (which are run by example()) instead of instructing the tester to do so. This can be temporarily circumvented during development by setting environment variable _R_CHECK_DONTTEST_EXAMPLES_ to a false value. PACKAGE INSTALLATION: * There is the beginnings of...

...iously type-checking was done on the replacement value and so this failed, whereas we now assume NULL can be promoted to any zero-length vector-like object. Other cases of a zero-length index are done more efficiently. o There is a new option in Rd markup of \donttest{} to mark example code that should be run by example() but not tested (e.g. because it might fail in some locales). o The error handler in the parser now reports line numbers for more syntax errors (MBCS and Unicode encoding errors, line length and context sta...

...iously type-checking was done on the replacement value and so this failed, whereas we now assume NULL can be promoted to any zero-length vector-like object. Other cases of a zero-length index are done more efficiently. o There is a new option in Rd markup of \donttest{} to mark example code that should be run by example() but not tested (e.g. because it might fail in some locales). o The error handler in the parser now reports line numbers for more syntax errors (MBCS and Unicode encoding errors, line length and context sta...