CRAN Package Check Results for Package R.filesets

Last updated on 2023-01-25 04:51:45 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 2.15.0 8.91 128.13 137.04 WARN
r-devel-linux-x86_64-debian-gcc 2.15.0 6.30 96.52 102.82 OK
r-devel-linux-x86_64-fedora-clang 2.15.0 167.47 OK
r-devel-linux-x86_64-fedora-gcc 2.15.0 167.35 OK
r-devel-windows-x86_64 2.15.0 19.00 0.00 19.00 FAIL
r-patched-linux-x86_64 2.15.0 8.24 116.69 124.93 OK
r-release-linux-x86_64 2.15.0 8.14 117.41 125.55 OK
r-release-macos-arm64 2.15.0 53.00 OK
r-release-macos-x86_64 2.15.0 68.00 OK
r-release-windows-x86_64 2.15.0 157.00 0.00 157.00 FAIL
r-oldrel-macos-arm64 2.15.0 51.00 OK
r-oldrel-macos-x86_64 2.15.0 64.00 OK
r-oldrel-windows-ix86+x86_64 2.15.0 16.00 197.00 213.00 OK

Check Details

Version: 2.15.0
Check: for code/documentation mismatches
Result: WARN
    Error in b[[2L]] : subscript out of bounds
    Calls: <Anonymous> -> vapply -> FUN
    Execution halted
Flavor: r-devel-linux-x86_64-debian-clang

Version: 2.15.0
Check: tests
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:
    39 8 1 g
    40 1 2 j
    41 1 1 r
    42 4 3 t
    43 2 7 g
    44 1 6 s
    45 6 10 f
    46 6 2 a
    47 2 4 e
    48 7 24 c
    49 8 1 g
    50 1 2 j
    >
    >
    >
    > ### * <FOOTER>
    > ###
    > cleanEx()
    > options(digits = 7L)
    > base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
    Time elapsed: 10.42 0.44 11.1 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: 2.15.0
Check: tests
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:
    39 8 1 g
    40 1 2 j
    41 1 1 r
    42 4 3 t
    43 2 7 g
    44 1 6 s
    45 6 10 f
    46 6 2 a
    47 2 4 e
    48 7 24 c
    49 8 1 g
    50 1 2 j
    >
    >
    >
    > ### * <FOOTER>
    > ###
    > cleanEx()
    > options(digits = 7L)
    > base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
    Time elapsed: 10.25 0.31 10.84 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-release-windows-x86_64