Last updated on 2024-12-31 09:49:44 CET.
| Package | FAIL | NOTE | OK |
|---|---|---|---|
| tibblify | 1 | 5 | 7 |
Current CRAN status: FAIL: 1, NOTE: 5, OK: 7
Version: 0.3.1
Check: Rd cross-references
Result: NOTE
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
guess_tspec.Rd: abort
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64
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.
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.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/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,
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.3.1
Check: PDF version of manual
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:
[[2]]$a
[1] 2
[[2]]$b
[[2]]$b$x
[1] "b"
[[2]]$b$y
[1] 2.5
>
>
>
> ### * <FOOTER>
> ###
> cleanEx()
> options(digits = 7L)
> base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
Time elapsed: 1.73 0.1 1.83 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
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.