similar to: CRAN packages mis-using \donttest : falsy

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 >

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

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

Is there a good strategy for testing examples which should not be run by default? For instance, 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

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

Hi, Paul: "if(!fda::CRAN())" runs code except with "R CMD check ?as-cran". I use it so CRAN checks skip examples that (a) need the Internet or (b) take too long for CRAN. Hope this helps. Spencer On 11/26/2014 10:45 AM, Paul Gilbert wrote: > Is there a good strategy for testing examples which should not be run > by default? For instance,

On 14-11-26 05:49 PM, Duncan Murdoch wrote: > On 26/11/2014, 1:45 PM, Paul Gilbert wrote: >> Is there a good strategy for testing examples which should not be run by >> default? For instance, 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

I am perplexed about NOTEs I get from Win Builder on my genridge package, https://github.com/friendly/genridge. It shows, e.g., Examples with CPU or elapsed time > 10s user system elapsed plot3d.ridge 12.4 0.05 12.45 However, if I run *exactly 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

Hi all, I''m having a problem with an Ajax.Request. I can''t figure out how I can pass an event (an onclick on a checkbox) which causes the Ajax Request, to be recognized in an onSuccess function. Here''s my simplified code: var RequiredField = Class.create(); RequiredField.prototype = { initialize: function(chkbox) { this.chkbox = chkbox; this.chkbox.onclick =

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

The build system rolled up R-4.4.0.tar.gz and R-4.4.0.tar.xz (codename "Puppy Cup") this morning. This is a major update, containing many new features and bug fixes. The list below details the changes in this release. You can get the source code from https://cran.r-project.org/src/base/R-4/R-4.4.0.tar.gz https://cran.r-project.org/src/base/R-4/R-4.4.0.tar.xz or wait for it to be

The build system rolled up R-4.4.0.tar.gz and R-4.4.0.tar.xz (codename "Puppy Cup") this morning. This is a major update, containing many new features and bug fixes. The list below details the changes in this release. You can get the source code from https://cran.r-project.org/src/base/R-4/R-4.4.0.tar.gz https://cran.r-project.org/src/base/R-4/R-4.4.0.tar.xz or wait for it to be

Hi everyone The following behavior (in R 3.6.1 and R-devel r77040) caught me by surprise today: truthy <- c(TRUE, FALSE) falsy <- c(FALSE, TRUE, FALSE) if (truthy) "check" #> Warning in if (truthy) "check": the condition has length > 1 and only the #> first element will be used #> [1] "check" if (falsy) "check" #> Warning in if

The build system rolled up R-4.0.0.tar.gz (codename "Arbor Day") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-4/R-4.0.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter Dalgaard These are

The build system rolled up R-4.0.0.tar.gz (codename "Arbor Day") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-4/R-4.0.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter Dalgaard These are

The build system rolled up R-4.0.0.tar.gz (codename "Arbor Day") this morning. The list below details the changes in this release. You can get the source code from http://cran.r-project.org/src/base/R-4/R-4.0.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. Binaries for various platforms will appear in due course. For the R Core Team, Peter Dalgaard These are

I've rolled up R-2.7.0.tar.gz a short while ago. This is a development release which contains a number of new features. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it (later today) from http://cran.r-project.org/src/base/R-2/R-2.7.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. In case of impatience, try

I've rolled up R-2.7.0.tar.gz a short while ago. This is a development release which contains a number of new features. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it (later today) from http://cran.r-project.org/src/base/R-2/R-2.7.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. In case of impatience, try

I'm using R to manipulate some data for testing nebulisers. I have a data frame as follows: Volt ABal 0.4208 A1 0.3982 AF 0.4353 B1 0.3954 BF 0.4355 C1 0.3975 CF 0.4345 I also have a calibration curve loaded Voltage NaF LogNaF 1 0.3588 20 1.30103 2 0.3990 100 2.00000 3 0.4391 500 2.69897 If I try to

Scenario: Using Dovecot 0.99.10.9 as pop3 server. With delete on retrival off. clients: outlook* Problem: Everytihng work perfectly, except that outlooks keeps re-downloading SOME mail over and over. Though it already got them. No obvious pattern which, but only a small percentage. First of I looked at dovecots UIDLs. Initialy I thought it's broken (see my previous thread) Sorry for even