Thank you! I added skip on CRAN to the time intensive tests, and it's
passing again. MUCH APPRECIATED!
On Tue, Jun 2, 2020 at 12:03 PM Uwe Ligges
wrote:
> Simply:
>
> ** running tests for arch 'i386' ... [14m] OK
>
> And the CRAN threshold for the whole package is 10 min. So only the
> tests f
Simply:
** running tests for arch 'i386' ... [14m] OK
And the CRAN threshold for the whole package is 10 min. So only the
tests for two architectures already take ~ 30 min here. which is too
much for CRAN.
Best,
Uwe Ligges
On 02.06.2020 16:13, Gábor Csárdi wrote:
Seems like your tests d
In my opinion, if you've tested on multiple Windows system that
you've done your due diligence and shouldn't worry too much about
win-builder hiccups ...
On Tue, Jun 2, 2020 at 10:09 AM Daniel Sjoberg
wrote:
>
> Hello List!
>
> I am prepping gtsummary for a new release, but I am running into a
Seems like your tests did not finish:
https://win-builder.r-project.org/SFSFeP44df58/examples_and_tests/tests_x64/testthat.Rout
Either they take too long, or they froze. You can use a different
testthat reporter, to see which one is stuck, e.g. like this:
https://github.com/cran/desc/blob/3e52b492
Hello List!
I am prepping gtsummary for a new release, but I am running into a problem
with the CRAN win-builder.
The package is passing checks on my local Windows machine, another local
Windows machine, on a GitHub Actions Windows machine (
https://github.com/ddsjoberg/gtsummary/runs/729569705?c
