* using log directory ‘/srv/hornik/tmp/CRAN/Sequential.Rcheck’ * using R Under development (unstable) (2023-10-23 r85401) * using platform: x86_64-pc-linux-gnu * R was compiled by Debian clang version 16.0.6 (15) GNU Fortran (Debian 13.2.0-4) 13.2.0 * running under: Debian GNU/Linux trixie/sid * using session charset: UTF-8 * checking for file ‘Sequential/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘Sequential’ version ‘4.3.1’ * checking CRAN incoming feasibility ... [3s/3s] Note_to_CRAN_maintainers Maintainer: ‘Ivair Ramos Silva ’ * 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 serialization versions ... OK * checking whether package ‘Sequential’ can be installed ... [12s/12s] OK * checking package directory ... OK * checking for future file timestamps ... 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 R files for non-ASCII characters ... OK * checking R files for syntax errors ... OK * checking whether the package can be loaded ... [0s/0s] 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 use of S3 registration ... 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 ... [31s/31s] OK * checking Rd files ... [0s/0s] NOTE checkRd: (-1) ConfidenceInterval.Binomial.Rd:22: Lost braces 22 | For two-tailed testing (code{Tailed="two"}), both lower and upper signaling thresholds must be informed through | ^ checkRd: (-1) Performance.AlphaSpend.Binomial.Rd:65: Lost braces 65 | The input \code{Statistic} specifies the scale selected by the user to inform \code{cvs.lower} and code{cvs.upper}among the classic methods: | ^ checkRd: (-1) Performance.Threshold.Binomial.Rd:30: Lost braces 30 | For two-tailed testing (code{Tailed="two"}), both lower and upper signaling thresholds must be informed through | ^ checkRd: (-1) Performance.Threshold.Binomial.Rd:51: Lost braces 51 | The input \code{Statistic} specifies the scale selected by the user to inform \code{CV.lower} and code{cvs.upper}among the classic methods: | ^ checkRd: (-1) Performance.Threshold.Poisson.Rd:35: Lost braces 35 | The inputs \code{CV.lower}, \code{CV.upper}, if two-tailed testing (code{Tailed="two"}), | ^ checkRd: (-1) Performance.Threshold.Poisson.Rd:45: Lost braces 45 | The input \code{Statistic} specifies the scale selected by the user to inform \code{CV.lower} and code{CV.upper}among the classic methods: | ^ * checking Rd metadata ... OK * checking Rd line widths ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... OK * checking for code/documentation mismatches ... OK * checking Rd \usage sections ... OK * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking examples ... [2s/2s] OK * checking PDF version of manual ... [5s/5s] OK * checking HTML version of manual ... [2s/2s] OK * checking for non-standard things in the check directory ... OK * checking for detritus in the temp directory ... OK * DONE Status: 1 NOTE