On 29.10.2022 14:14, Jamie Lentin wrote:
On 2022-10-28 20:48, Ying Li via R-package-devel wrote:
Flavor: r-devel-windows-x86_64
Check: examples, Result: NOTE
Examples with CPU (user + system) or elapsed time > 10s
user system elapsed
RDM 40.05 0.89 40.94
Explain: This is becaus
> Jamie Lentin
> on Sat, 29 Oct 2022 13:14:20 +0100 writes:
> On 2022-10-28 20:48, Ying Li via R-package-devel wrote:
>>> Flavor: r-devel-windows-x86_64 Check: examples, Result:
>>> NOTE Examples with CPU (user + system) or elapsed time >
>>> 10s user system elapsed RD
On 2022-10-28 20:48, Ying Li via R-package-devel wrote:
Flavor: r-devel-windows-x86_64
Check: examples, Result: NOTE
Examples with CPU (user + system) or elapsed time > 10s
user system elapsed
RDM 40.05 0.89 40.94
Explain: This is because a large dataset is used in the example. An
I run into this all the time. The trick is to find a minimal example that the
package will work with that shows how to make a call, and allows for CRAN,
especially on new submissions, to test to some extent that the function works.
For more real-life examples, write a good vignette that use
This is definitely not a false positive. Find a way to not run long calcs
during the CRAN build. There is no alternative.
One way this can be done is by only running your examples when an environment
variable of your choosing exists. Since CRAN machines won't configure that
variable, you can ge
