CRAN Package Check Results for Package ptest

Last updated on 2024-02-27 07:54:56 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.0-8 11.86 108.45 120.31 NOTE
r-devel-linux-x86_64-debian-gcc 1.0-8 8.57 81.70 90.27 NOTE
r-devel-linux-x86_64-fedora-clang 1.0-8 146.01 NOTE
r-devel-linux-x86_64-fedora-gcc 1.0-8 153.97 NOTE
r-devel-windows-x86_64 1.0-8 14.00 100.00 114.00 NOTE
r-patched-linux-x86_64 1.0-8 16.89 106.33 123.22 OK
r-release-linux-x86_64 1.0-8 11.50 105.44 116.94 OK
r-release-macos-arm64 1.0-8 53.00 OK
r-release-macos-x86_64 1.0-8 84.00 OK
r-release-windows-x86_64 1.0-8 16.00 116.00 132.00 OK
r-oldrel-macos-arm64 1.0-8 54.00 OK
r-oldrel-windows-x86_64 1.0-8 15.00 116.00 131.00 OK

Check Details

Version: 1.0-8
Check: Rd files
Result: NOTE checkRd: (-1) pgram.Rd:12: Lost braces; missing escapes or markup? 12 | \item{fr}{use "default" for usual Fourier frequencies, {1/n, ..., floor(n/2)/n}. | ^ 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: 1.0-8
Check: Rd \usage sections
Result: NOTE Documented arguments not in \usage in Rd file 'GetFitHReg.Rd': ‘z’ Functions with \usage entries need to have the appropriate \alias entries, and all their arguments documented. The \usage entries must correspond to syntactically valid R code. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual. 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

Version: 1.0-8
Check: compiled code
Result: NOTE File ‘ptest/libs/ptest.so’: Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’ It is good practice to register native routines and to disable symbol search. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc