• using R version 4.4.0 alpha (2024-03-31 r86238)
• using platform: aarch64-apple-darwin20
• R was compiled by     Apple clang version 14.0.0 (clang-1400.0.29.202)     GNU Fortran (GCC) 12.2.0
• running under: macOS Ventura 13.4
• using session charset: UTF-8
• checking for file ‘cfbfastR/DESCRIPTION’ ... OK
• this is package ‘cfbfastR’ version ‘1.9.0’
• package encoding: UTF-8
• checking package namespace information ... OK
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... OK
• checking for executable files ... OK
• checking for hidden files and directories ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking whether package ‘cfbfastR’ can be installed ... [8s/14s] OK See the install log for details.
• checking installed package size ... OK
• checking package directory ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level files ... OK
• checking for left-over files ... OK
• checking index information ... OK
• checking package subdirectories ... OK
• checking code files for non-ASCII characters ... OK
• checking R files for syntax errors ... OK
• checking whether the package can be loaded ... [2s/3s] OK
• checking whether the package can be loaded with stated dependencies ... [2s/3s] OK
• checking whether the package can be unloaded cleanly ... [2s/3s] OK
• checking whether the namespace can be loaded with stated dependencies ... [2s/3s] OK
• checking whether the namespace can be unloaded cleanly ... [2s/3s] OK
• checking loading without being on the library search path ... [2s/3s] OK
• checking whether startup messages can be suppressed ... [2s/3s] OK
• checking dependencies in R code ... OK
• checking S3 generic/method consistency ... OK
• checking replacement functions ... OK
• checking foreign function calls ... OK
• checking R code for possible problems ... [7s/11s] OK
• checking Rd files ... [1s/1s] NOTE checkRd: (-1) helpers_pbp.Rd:336: Lost braces in \itemize; meant \describe ? checkRd: (-1) helpers_pbp.Rd:337: Lost braces in \itemize; meant \describe ? checkRd: (-1) helpers_pbp.Rd:338: Lost braces in \itemize; meant \describe ? checkRd: (-1) helpers_pbp.Rd:339: Lost braces in \itemize; meant \describe ? checkRd: (-1) helpers_pbp.Rd:340: Lost braces in \itemize; meant \describe ? checkRd: (-1) helpers_pbp.Rd:341: Lost braces in \itemize; meant \describe ? checkRd: (-1) helpers_pbp.Rd:390: Lost braces in \itemize; meant \describe ? checkRd: (-1) helpers_pbp.Rd:391: Lost braces in \itemize; meant \describe ? checkRd: (-1) helpers_pbp.Rd:392: Lost braces in \itemize; meant \describe ? checkRd: (-1) helpers_pbp.Rd:393: Lost braces in \itemize; meant \describe ? checkRd: (-1) helpers_pbp.Rd:394: Lost braces in \itemize; meant \describe ? checkRd: (-1) update_cfb_db.Rd:46-48: Lost braces in \itemize; meant \describe ? checkRd: (-1) update_cfb_db.Rd:49-52: Lost braces in \itemize; meant \describe ?
• checking Rd metadata ... OK
• checking Rd cross-references ... OK
• checking for missing documentation entries ... OK
• checking for code/documentation mismatches ... OK
• checking Rd \usage sections ... NOTE Documented arguments not in \usage in Rd file 'create_epa.Rd':   ‘clean_pbp_dat’ ‘df’ 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.
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking contents of ‘data’ directory ... OK
• checking data for non-ASCII characters ... [0s/0s] OK
• checking LazyData ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking examples ... [2s/3s] OK
• checking for unstated dependencies in ‘tests’ ... OK
• checking tests ... [3s/4s] OK   Running ‘testthat.R’ [3s/4s]
• checking PDF version of manual ... [7s/7s] OK
• DONE Status: 2 NOTEs
• using check arguments '--no-clean-on-error '