CRAN Package Check Results for Package timeplyr

Last updated on 2024-07-01 03:49:26 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.8.1 33.55 269.75 303.30 NOTE
r-devel-linux-x86_64-debian-gcc 0.8.1 25.02 202.06 227.08 NOTE
r-devel-linux-x86_64-fedora-clang 0.8.1 411.29 NOTE
r-devel-linux-x86_64-fedora-gcc 0.8.1 386.33 NOTE
r-devel-windows-x86_64 0.8.1 33.00 213.00 246.00 NOTE
r-patched-linux-x86_64 0.8.1 35.35 211.97 247.32 OK
r-release-linux-x86_64 0.8.1 23.37 260.75 284.12 OK
r-release-macos-arm64 0.8.1 99.00 OK
r-release-macos-x86_64 0.8.1 287.00 OK
r-release-windows-x86_64 0.8.1 32.00 214.00 246.00 OK
r-oldrel-macos-arm64 0.8.1 95.00 OK
r-oldrel-macos-x86_64 0.8.1 234.00 OK
r-oldrel-windows-x86_64 0.8.1 40.00 270.00 310.00 OK

Check Details

Version: 0.8.1
Check: compiled code
Result: NOTE File ‘timeplyr/libs/timeplyr.so’: Found non-API call to R: ‘STRING_PTR’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. See section ‘Moving into C API compliance’ in the ‘Writing R Extensions’ manual for issues with use of non-API entry points. Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc

Version: 0.8.1
Check: compiled code
Result: NOTE File ‘timeplyr/libs/timeplyr.so’: Found non-API call to R: ‘STRING_PTR’ 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-linux-x86_64-fedora-clang

Version: 0.8.1
Check: compiled code
Result: NOTE File ‘timeplyr/libs/timeplyr.so’: Found non-API call to R: ‘STRING_PTR’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-fedora-gcc

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