CRAN Package Check Results for Package tibblify

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

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.3.1 15.54 113.98 129.52 NOTE
r-devel-linux-x86_64-debian-gcc 0.3.1 11.34 81.84 93.18 NOTE
r-devel-linux-x86_64-fedora-clang 0.3.1 172.37 NOTE
r-devel-linux-x86_64-fedora-gcc 0.3.1 173.22 NOTE
r-devel-windows-x86_64 0.3.1 25.00 106.00 131.00 NOTE
r-patched-linux-x86_64 0.3.1 18.01 108.03 126.04 OK
r-release-linux-x86_64 0.3.1 14.60 104.78 119.38 OK
r-release-macos-arm64 0.3.1 48.00 OK
r-release-macos-x86_64 0.3.1 78.00 OK
r-release-windows-x86_64 0.3.1 25.00 106.00 131.00 OK
r-oldrel-macos-arm64 0.3.1 56.00 OK
r-oldrel-macos-x86_64 0.3.1 97.00 OK
r-oldrel-windows-x86_64 0.3.1 29.00 125.00 154.00 OK

Check Details

Version: 0.3.1
Check: compiled code
Result: NOTE File ‘tibblify/libs/tibblify.so’: Found non-API calls to R: ‘FRAME’, ‘HASHTAB’, ‘PRENV’, ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_findVarInFrame3’, ‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_FORMALS’, ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’, ‘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.3.1
Check: dependencies in R code
Result: NOTE Namespace in Imports field not imported from: ‘lifecycle’ All declared Imports should be used. Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 0.3.1
Check: compiled code
Result: NOTE File ‘tibblify/libs/tibblify.so’: Found non-API calls to R: ‘FRAME’, ‘HASHTAB’, ‘PRENV’, ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_findVarInFrame3’, ‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_FORMALS’, ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’, ‘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.3.1
Check: compiled code
Result: NOTE File ‘tibblify/libs/tibblify.so’: Found non-API calls to R: ‘FRAME’, ‘HASHTAB’, ‘PRENV’, ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_findVarInFrame3’, ‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_FORMALS’, ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’, ‘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.3.1
Check: compiled code
Result: NOTE File 'tibblify/libs/x64/tibblify.dll': Found non-API calls to R: 'FRAME', 'HASHTAB', 'PRENV', 'PRVALUE', 'R_PromiseExpr', 'Rf_findVarInFrame3', 'SETLENGTH', 'SET_BODY', 'SET_CLOENV', 'SET_FORMALS', 'SET_GROWABLE_BIT', 'SET_TRUELENGTH', '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