[R-pkg-devel] CRAN pretest: Overall checktime 14 min > 10 min

2018-05-21 Thread Chris Njuguna
Hi, I am trying to submit an update to the Rnightlights package that I maintain (on CRAN at https://cran.r-project.org/package=Rnightlights and source code on Github at https://github.com/chrisvwn/Rnightlights). I am getting a checktime note specifically for checks on the r-devel-windows-ix86+x86

Re: [R-pkg-devel] CRAN pretest: Overall checktime 14 min > 10 min

2018-05-21 Thread Dirk Eddelbuettel
I can't speak to the recent increase on Windows. It may be load; it may be related to R 3.5.0 --- but I'd even whittle things down from 5+ minutes. At one point in the past we were told to aim for 1 minute, give or take. So e.g. Rcpp has been using a scheme for _many_ years where I take a cue fr

Re: [R-pkg-devel] CRAN pretest: Overall checktime 14 min > 10 min

2018-05-21 Thread Chris Njuguna
Thank you for this! It makes a lot of sense. I will adopt this version naming and testing scheme. I do have some internet-based tests including a small download. These could be adding some variability so will move them out of the regular tests. Christopher Njuguna cell: +254 717 916 343 cell:

Re: [R-pkg-devel] CRAN pretest: Overall checktime 14 min > 10 min

2018-05-21 Thread Uwe Ligges
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 ale

Re: [R-pkg-devel] CRAN pretest: Overall checktime 14 min > 10 min

2018-05-21 Thread Dirk Eddelbuettel
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 t

Re: [R-pkg-devel] CRAN pretest: Overall checktime 14 min > 10 min

2018-05-21 Thread Uwe Ligges
On 21.05.2018 18:04, Dirk Eddelbuettel wrote: 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 shortl

Re: [R-pkg-devel] CRAN pretest: Overall checktime 14 min > 10 min

2018-05-21 Thread Chris Njuguna
Thanks Uwe, I think the timeouts are helpful also in encouraging better coding practices. I will try to limit my tests as described by Dirk especially since I am planning to increase my code test coverage. Is it possible to get the test timing breakdowns for each flavor? Christopher Njuguna cell:

Re: [R-pkg-devel] CRAN pretest: Overall checktime 14 min > 10 min

2018-05-21 Thread Uwe Ligges
Well, on incoming, we only check on two systems and the Windows timings will be reported in the message you receive, you can also see them when using the winbuilder service. For some of the other OS/ R flavors, you can see them after they are published on CRAN on the check summary pagesa on CR

Re: [R-pkg-devel] CRAN pretest: Overall checktime 14 min > 10 min

2018-05-21 Thread Chris Njuguna
Okay, thanks. And thank you all for putting in your time and effort! Christopher Njuguna cell: +254 717 916 343 cell: +254 739 956 510 gchat: chris.njuguna skype: christopher.njuguna twitter: @chrisnjuguna On Mon, May 21, 2018 at 7:20 PM, Uwe Ligges wrote: > Well, on incoming, we only check on