CRAN Package Check Results for Maintainer ‘Kathleen M Gates <gateskm at email.unc.edu>’

Last updated on 2024-10-06 07:50:56 CEST.

Package FAIL OK
gimme 13
perturbR 1 12

Package gimme

Current CRAN status: OK: 13

Package perturbR

Current CRAN status: FAIL: 1, OK: 12

Version: 0.1.3
Check: PDF version of manual
Result: FAIL 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: 14 0 0 0 0 15 0 0 2 0 16 0 0 0 0 17 0 0 0 2 18 0 0 0 0 19 2 0 0 0 20 0 0 0 0 21 0 0 0 0 22 0 0 0 2 23 0 0 0 0 24 0 0 0 0 25 2 0 0 0 > > > > ### * <FOOTER> > ### > cleanEx() > options(digits = 7L) > base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n") Time elapsed: 1.72 0.15 1.87 NA NA > grDevices::dev.off() null device 1 > ### > ### Local variables: *** > ### mode: outline-minor *** > ### outline-regexp: "\\(> \\)?### [*]+" *** > ### End: *** > quit('no') ======== End of example output (where/before crash/hang up occured ?) ======== Flavor: r-devel-windows-x86_64