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