So your windows installation of R-3.4.0 can solve this in 600ms? Or is
yoiur another OS?
ah, yes, another OS. it turns out on windows this takes 6 seconds. the
issue is that we only load imports on demand (not in our NAMESPACE),
there's a behemoth dependency chain that that analysis invokes,
On 05.06.2017 14:48, Jonathon Love wrote:
hi dason,
yes, it looks like it's taking 10 seconds.
10 seconds still seems unusually long, and a lot longer than 600ms.
So your windows installation of R-3.4.0 can solve this in 600ms? Or is
yoiur another OS?
For winbuilder, it could be it was h
hi dason,
yes, it looks like it's taking 10 seconds.
10 seconds still seems unusually long, and a lot longer than 600ms.
any other suggestions as to what might be going on here?
with thanks
jonathon
On 5/6/17 22:36, Dason Kurkiewicz wrote:
The relevant output is below:
* checking examples
The relevant output is below:
* checking examples ...
** running examples for arch 'i386' ... [24s] NOTE
Examples with CPU or elapsed time > 10s
user system elapsed
cfa 8.05 0.36 10.08
** running examples for arch 'x64' ... [28s] NOTE
Examples with CPU or elapsed time > 10s
user syste
hi,
i've uploaded a version of my package to the win-builder service, but it
is reporting that one of my tests takes > 10 seconds to run. examining
the log here:
https://win-builder.r-project.org/BvR4nreDE9qP/00check.log
the win-builder is taking 24 and 28 seconds to run this test.
on my lo