On 01.07.2018 02:49, Michael Levy wrote:
Thanks Uwe. Seems I need to overhaul my tests...
Of course you can keep these for yourself and skip less important tests
unless some env var is set that you only define on your machine.
Best,
Uwe Ligges
--
Michael Levy
970-426-5389
On Sat, Jun 30, 2018 at 2:59 PM Uwe Ligges
<lig...@statistik.tu-dortmund.de
<mailto:lig...@statistik.tu-dortmund.de>> wrote:
Wekk, after 20 min the process is killed. If you spend 17 min in i386,
and some time in the previous part of the checks, there is not much
time
left for the 64-bit checks ....
If you aim to submit the package to CRAN, note that the overall check
time (including both architectures) should not exceed 10 minutes.
Best,
Uwe Ligges
On 30.06.2018 20:36, Michael Levy wrote:
> Hi all,
>
>
>
> My package's tests seem to be hanging on win-builder's x64 build
for all
> three R releases, but they complete okay on win-builder i386 and on
> AppVeyor x64 (and on other platforms). The tests take a while to
complete,
> so I've split them into multiple files so that some output comes
back every
> few minutes. Any idea how I might fix this? Thanks.
>
>
>
> ** running tests for arch 'i386' ... [17m] OK
>
> Running 'testthat-1.R' [103s]
>
> Running 'testthat-2.R' [477s]
>
> Running 'testthat-3.R' [425s]
>
> Running 'testthat-4.R' [7s]
>
> ** running tests for arch 'x64' ... ERROR
>
> Check process probably crashed or hung up for 20 minutes ... killed
>
> Most likely this happened in the example checks (?),
>
> if not, ignore the following last lines of example output:
>
>
>
> ======== End of example output (where/before crash/hang up occured ?)
> ========
>
>
>
>
>
>
> [[alternative HTML version deleted]]
>
> ______________________________________________
> R-package-devel@r-project.org
<mailto:R-package-devel@r-project.org> mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
>
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
