Last updated on 2024-12-04 07:52:04 CET.
| Package | FAIL | NOTE | OK |
|---|---|---|---|
| AggregateR | 1 | 8 | 4 |
| DecorateR | 8 | 5 |
Current CRAN status: FAIL: 1, NOTE: 8, OK: 4
Version: 0.1.1
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:
> ##D
> ##D #ref=FALSE, example 3
> ##D #example 1 and 2 are more memory efficient than example 3
> ##D (DT = data.table(a=c("a","b"),b=c("c","c")))
> ##D d2 <- dummy(DT, ref=FALSE)
> ##D DT[] #DT has not changed
> ##D d[]
> ##D # deleting DT after dummy finishes would result in the same final
> ##D # memory footprint as example 1 and 2, except that in example 3
> ##D # memory usage is higher when dummy is being executed, and this may be
> ##D # problematic when DT is large.
> ## End(Not run)
>
>
>
> ### * <FOOTER>
> ###
> cleanEx()
> options(digits = 7L)
> base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
Time elapsed: 1.59 0.19 1.8 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
Version: 0.1.1
Check: LazyData
Result: NOTE
'LazyData' is specified without a 'data' directory
Flavors: r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Current CRAN status: NOTE: 8, OK: 5
Version: 0.1.2
Check: LazyData
Result: NOTE
'LazyData' is specified without a 'data' directory
Flavors: r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64