• 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 ‘ffstream/DESCRIPTION’ ... OK
• this is package ‘ffstream’ version ‘0.1.7.2’
• 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 ‘ffstream’ can be installed ... [28s/29s] OK See the install log for details.
• used C++ compiler: ‘Apple clang version 14.0.0 (clang-1400.0.29.202)’
• used SDK: ‘MacOSX11.3.sdk’
• checking installed package size ... NOTE   installed size is 8.6Mb   sub-directories of 1Mb or more:     libs 8.2Mb
• checking package directory ... OK
• checking ‘build’ 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 ... [0s/1s] OK
• checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
• checking whether the package can be unloaded cleanly ... [0s/0s] OK
• checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK
• checking whether the namespace can be unloaded cleanly ... [0s/0s] OK
• checking loading without being on the library search path ... [0s/0s] 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 ... [3s/3s] OK
• checking Rd files ... [0s/0s] OK
• 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 'checkStream.Rd':   ‘skipChecks’ Documented arguments not in \usage in Rd file 'cpp_detectCUSUMMeanSinglePrechange.Rd':   ‘BL’ Documented arguments not in \usage in Rd file 'cpp_detectEWMAMeanSinglePrechange.Rd':   ‘BL’ Documented arguments not in \usage in Rd file 'makeStreamMeanChangeR.Rd':   ‘x’ Documented arguments not in \usage in Rd file 'update_Omega.Rd':   ‘m_new’ 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 line endings in C/C++/Fortran sources/headers ... OK
• checking compiled code ... OK
• checking installed files from ‘inst/doc’ ... OK
• checking files in ‘vignettes’ ... OK
• checking examples ... [0s/1s] OK
• checking for unstated dependencies in ‘tests’ ... OK
• checking tests ... [2s/2s] OK   Running ‘testthat.R’ [2s/2s]
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes ... NOTE Package vignette without corresponding tangle output:   ‘intro.Rmd’
• checking re-building of vignette outputs ... [6s/6s] OK
• checking PDF version of manual ... [4s/5s] OK
• DONE Status: 3 NOTEs
• using check arguments '--no-clean-on-error '