Re: [R-pkg-devel] email misleading: checking CRAN incoming feasibility ... NOTE Maintainer

2020-06-08 Thread Duncan Murdoch
The built-in way is to put those tests in a separate directory, and specify that directory when you run R CMD check. For example, rgl has directory "inst/slowTests", and I use these options to R CMD check: --test-dir=inst/slowTests Duncan Murdoch On 08/06/2020 10:52 a.m., Spencer Graves wro

Re: [R-pkg-devel] email misleading: checking CRAN incoming feasibility ... NOTE Maintainer

2020-06-08 Thread Daniel Lüdecke
s: https://github.com/easystats/insight/blob/cddc6df6783aae859f2b707dd5a938493bff3aaa/tests/testthat/test-spatial.R#L141 Hope this helps! Best Daniel -----Ursprüngliche Nachricht----- Von: R-package-devel Im Auftrag von Spencer Graves Gesendet: Montag, 8. Juni 2020 16:53 An: r-package-devel@r-proj

Re: [R-pkg-devel] email misleading: checking CRAN incoming feasibility ... NOTE Maintainer

2020-06-08 Thread Uwe Ligges
On 08.06.2020 17:02, Gábor Csárdi wrote: On Mon, Jun 8, 2020 at 3:58 PM Uwe Ligges wrote: [...] Nor do I how they can find out, as our idea is that CRAN cannot be special cased. If you want to run additional tests, you can execute them if some env var is set that you define on machines where

Re: [R-pkg-devel] email misleading: checking CRAN incoming feasibility ... NOTE Maintainer

2020-06-08 Thread Gábor Csárdi
On Mon, Jun 8, 2020 at 3:58 PM Uwe Ligges wrote: [...] > Nor do I how they can find out, as our idea is that CRAN cannot be > special cased. > If you want to run additional tests, you can execute them if some env > var is set that you define on machines where you want to run the > additional tests

Re: [R-pkg-devel] email misleading: checking CRAN incoming feasibility ... NOTE Maintainer

2020-06-08 Thread Uwe Ligges
On 08.06.2020 16:52, Spencer Graves wrote: Hi, Uwe et al.:   What's the preferred way to eliminate tests on CRAN that the maintainer still wants to run on other platforms?   For several years, I've been using "if(!fda::CRAN()){...}". I've been told that I should NOT do that, b

Re: [R-pkg-devel] email misleading: checking CRAN incoming feasibility ... NOTE Maintainer

2020-06-08 Thread Spencer Graves
Hi, Uwe et al.:   What's the preferred way to eliminate tests on CRAN that the maintainer still wants to run on other platforms?   For several years, I've been using "if(!fda::CRAN()){...}". I've been told that I should NOT do that, but it has worked for me, and I haven't found any

Re: [R-pkg-devel] email misleading: checking CRAN incoming feasibility ... NOTE Maintainer

2020-06-08 Thread stefano
Hello Uwe, OK sorry for that. Best wishes. *Stefano * Stefano Mangiola | Postdoctoral fellow Papenfuss Laboratory The Walter Eliza Hall Institute of Medical Research +61 (0)466452544 Il giorno mar 9 giu 2020 alle ore 00:40 Uwe Ligges < lig...@statistik.tu-dortmund.de> ha scritto: > > >

Re: [R-pkg-devel] email misleading: checking CRAN incoming feasibility ... NOTE Maintainer

2020-06-08 Thread Uwe Ligges
On 08.06.2020 16:26, stefano wrote: Hello, I would like to point out that I (and others in various forums) find that the CRAN check with the note : *checking CRAN incoming feasibility ... NOTEMaintainer* Not true, it also says Flavor: r-devel-windows-ix86+x86_64 Check: running examples

[R-pkg-devel] email misleading: checking CRAN incoming feasibility ... NOTE Maintainer

2020-06-08 Thread stefano
Hello, I would like to point out that I (and others in various forums) find that the CRAN check with the note : *checking CRAN incoming feasibility ... NOTEMaintainer* Triggers an email saying 1) *package nanny_0.1.7.tar.gz does not pass the incoming checks automatically* 2) *Please fix all