CRAN Package Check Results for Package clock

Last updated on 2024-07-25 00:51:53 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.7.1 204.37 253.85 458.22 NOTE
r-devel-linux-x86_64-debian-gcc 0.7.1 137.36 189.43 326.79 NOTE
r-devel-linux-x86_64-fedora-clang 0.7.1 593.98 NOTE
r-devel-linux-x86_64-fedora-gcc 0.7.1 631.01 NOTE
r-devel-windows-x86_64 0.7.1 130.00 275.00 405.00 NOTE
r-patched-linux-x86_64 0.7.0 162.55 242.88 405.43 OK
r-release-linux-x86_64 0.7.1 160.51 243.58 404.09 OK
r-release-macos-arm64 0.7.1 161.00 NOTE
r-release-macos-x86_64 0.7.1 369.00 NOTE
r-release-windows-x86_64 0.7.0 145.00 261.00 406.00 OK
r-oldrel-macos-arm64 0.7.1 165.00 ERROR
r-oldrel-macos-x86_64 0.7.1 220.00 ERROR
r-oldrel-windows-x86_64 0.7.1 174.00 321.00 495.00 OK

Check Details

Version: 0.7.1
Check: compiled code
Result: NOTE File ‘clock/libs/clock.so’: Found non-API calls to R: ‘SETLENGTH’, ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. 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

Version: 0.7.1
Check: compiled code
Result: NOTE File 'clock/libs/x64/clock.dll': Found non-API calls to R: 'SETLENGTH', 'SET_GROWABLE_BIT', 'SET_TRUELENGTH' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-devel-windows-x86_64

Version: 0.7.1
Check: installed package size
Result: NOTE installed size is 18.3Mb sub-directories of 1Mb or more: libs 16.4Mb Flavors: r-release-macos-arm64, r-release-macos-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64

Version: 0.7.1
Check: running R code from vignettes
Result: ERROR Errors in running code in vignettes: when running code in ‘clock.Rmd’ ... > date_build(2019, 2, 1:5) [1] "2019-02-01" "2019-02-02" "2019-02-03" "2019-02-04" "2019-02-05" > date_build(2019, 1:12, 31) When sourcing ‘clock.R’: Error: Invalid date found at location 2. ℹ Resolve invalid date issues by specifying the `invalid` argument. Execution halted when running code in ‘faq.Rmd’ ... <year_month_day<day>[1]> [1] "2019-02-05" > add_days(x, 1) When sourcing ‘faq.R’: Error: Can't perform this operation on a <clock_year_month_day>. ℹ Do you need to convert to a time point first? ℹ Use `as_naive_time()` or `as_sys_time()` to convert to a time point. Execution halted when running code in ‘recipes.Rmd’ ... [6] "2019-11-01" "2020-01-01" "2020-03-01" "2020-05-01" "2020-07-01" > date_seq(date_build(2019, 1, 1), to = date_build(2019, + 10, 2), by = duration_months(2)) When sourcing ‘recipes.R’: Error: All components of `from` and `to` more precise than "month" must match. ℹ `from` is "2019-01-01". ℹ `to` is "2019-10-02". Execution halted ‘clock.Rmd’ using ‘UTF-8’... failed ‘faq.Rmd’ using ‘UTF-8’... failed ‘recipes.Rmd’ using ‘UTF-8’... failed Flavors: r-oldrel-macos-arm64, r-oldrel-macos-x86_64