On 23.11.2020 04:13, Roy Mendelssohn - NOAA Federal wrote:
I have found win-builder timings come close, but only close. My experience is
that the CRAN timings were uniformly slower than those on win-builder. But I
also find that I can get quite significant differences between
win-builder
I have found win-builder timings come close, but only close. My experience is
that the CRAN timings were uniformly slower than those on win-builder. But I
also find that I can get quite significant differences between
win-builder-release and win-builder-devel. So I also take the slowest that
And one more (last for a while): presumably there is no way to check
CRAN windows timing without submitting to CRAN ... ? (I will obviously
do my best by doing arithmetic on the tests that I set to be skipped,
but it would be nice to be able to double-check without wasting
everyone's time ..
Thanks all for the help. The reward (as usual) is another dumb
question.
If I add up the elapsed times listed in
https://win-builder.r-project.org/incoming_pretest/lme4_1.1-26_20201122_184744/Windows/examples_and_tests/examples_x64/lme4-Ex.timings
I get 21.43 seconds. But the output in
Thanks Dirk. Yes, for lme4 the tests for each archiecture take longer
than 5 min, so the overall check time exceeds 10 min.
So one can follow Dirk's advise.
As a general remark for others who will read this in the future:
tests should test the software, but it is generally not important to
hav
On 22 November 2020 at 13:44, Ben Bolker wrote:
|My current guess is that the problem is with the too-long check time on
Windows (NOTE: "Overall checktime 18 min > 10 min")
Yes.
| I guess I have to get busy setting more tests and examples to skip-on-CRAN
(kind of a pain as there's no l
My submission from auto-check, and I'm not sure why because Windows and Debian checks
both list "OK" and there are no unresolved problems on the CRAN status ...
My current guess is that the problem is with the too-long check time on Windows (NOTE:
"Overall checktime 18 min > 10 min")
I gu
