CRAN Package Check Results for Package benchr

Last updated on 2021-06-24 10:52:16 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.2.5 34.86 37.84 72.70 NOTE
r-devel-linux-x86_64-debian-gcc 0.2.5 18.62 30.10 48.72 NOTE
r-devel-linux-x86_64-fedora-clang 0.2.5 96.92 NOTE
r-devel-linux-x86_64-fedora-gcc 0.2.5 81.78 NOTE
r-devel-windows-x86_64 0.2.5 34.00 77.00 111.00 NOTE
r-devel-windows-x86_64-gcc10-UCRT 0.2.5 ERROR
r-patched-linux-x86_64 0.2.5 25.97 36.25 62.22 NOTE
r-patched-solaris-x86 0.2.5 103.00 NOTE
r-release-linux-x86_64 0.2.5 25.65 36.08 61.73 NOTE
r-release-macos-arm64 0.2.5 NOTE
r-release-macos-x86_64 0.2.5 NOTE
r-release-windows-ix86+x86_64 0.2.5 63.00 113.00 176.00 NOTE
r-oldrel-macos-x86_64 0.2.5 OK

Check Details

Version: 0.2.5
Check: LazyData
Result: NOTE
     'LazyData' is specified without a 'data' directory
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64, r-devel-windows-x86_64-gcc10-UCRT, r-patched-linux-x86_64, r-patched-solaris-x86, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-ix86+x86_64

Version: 0.2.5
Check: examples
Result: ERROR
    Running examples in 'benchr-Ex.R' failed
    The error most likely occurred in:
    
    > ### Name: print.benchmark
    > ### Title: Print method for the 'benchmark' timings.
    > ### Aliases: print.benchmark print.summaryBenchmark
    >
    > ### ** Examples
    >
    > a1 <- a2 <- a3 <- a4 <- numeric(0)
    > res <- benchmark(
    + a1 <- c(a1, 1),
    + a2 <- append(a2, 1),
    + a3[length(a3) + 1] <- 1,
    + a4[[length(a4) + 1]] <- 1
    + )
    0% 10 20 30 40 50 60 70 80 90 100%
    [----|----|----|----|----|----|----|----|----|----|
    **************************************************|
    Error in benchmark(a1 <- c(a1, 1), a2 <- append(a2, 1), a3[length(a3) + :
     All timed evaluations were either smaller than the estimated
     timer error or zero. The most likely cause is a low resolution clock.
    Execution halted
Flavor: r-devel-windows-x86_64-gcc10-UCRT

Version: 0.2.5
Check: tests
Result: ERROR
     Running 'tinytest.R'
    Running the tests in 'tests/tinytest.R' failed.
    Last 13 lines of output:
     Running test-benchmark.R.............. 18 tests <1b>[0;32mOK<1b>[0m
     Running test-benchmark.R.............. 19 tests <1b>[0;32mOK<1b>[0m
     Running test-benchmark.R.............. 20 tests <1b>[0;32mOK<1b>[0m
     Running test-benchmark.R.............. 21 tests <1b>[0;32mOK<1b>[0m 0% 10 20 30 40 50 60 70 80 90 100%
     [----|----|----|----|----|----|----|----|----|----|
     **************************************************|
     Error in benchr::benchmark(1 + 1, times = 1L, gcDuring = TRUE) :
     All timed evaluations were either smaller than the estimated
     timer error or zero. The most likely cause is a low resolution clock.
     Calls: <Anonymous> ... run_test_dir -> lapply -> FUN -> eval -> eval -> <Anonymous>
     In addition: Warning message:
     In benchr::benchmark(1 + 1, 2 + 2) :
     Could not measure a positive execution time for
     199 evaluations.
     Execution halted
Flavor: r-devel-windows-x86_64-gcc10-UCRT