* using log directory 'd:/Rcompile/CRANpkg/local/4.4/lmtestrob.Rcheck' * using R version 4.4.0 RC (2024-04-16 r86468 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 13.2.0 GNU Fortran (GCC) 13.2.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * checking for file 'lmtestrob/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'lmtestrob' version '0.1' * 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 hidden files and directories ... OK * checking for portable file names ... OK * checking whether package 'lmtestrob' can be installed ... OK * 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 ... [0s] OK * checking whether the package can be loaded with stated dependencies ... [0s] OK * checking whether the package can be unloaded cleanly ... [0s] OK * checking whether the namespace can be loaded with stated dependencies ... [0s] OK * checking whether the namespace can be unloaded cleanly ... [0s] OK * checking loading without being on the library search path ... [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 ... [2s] OK * checking Rd files ... [0s] NOTE checkRd: (-1) robfmtest.Rd:24: Lost braces; missing escapes or markup? 24 | an optional data frame containing the variables in the model. If not found in data, the variables are taken from \code{environment(formula)}, typically the environment from which {robfmtest} is called. | ^ checkRd: (-1) robfmtest.Rd:37: Lost braces; missing escapes or markup? 37 | Since the classical tests including {resettest}, {raintest} and {harvtest} implemented in {lmtest} are not resistant to outliers and can become misleading even in the presence of one outlier, we provide a test which is resistant to outliers. The price to pay for robustness is a small loss of power, when the model holds exactly. | ^ checkRd: (-1) robfmtest.Rd:37: Lost braces; missing escapes or markup? 37 | Since the classical tests including {resettest}, {raintest} and {harvtest} implemented in {lmtest} are not resistant to outliers and can become misleading even in the presence of one outlier, we provide a test which is resistant to outliers. The price to pay for robustness is a small loss of power, when the model holds exactly. | ^ checkRd: (-1) robfmtest.Rd:37: Lost braces; missing escapes or markup? 37 | Since the classical tests including {resettest}, {raintest} and {harvtest} implemented in {lmtest} are not resistant to outliers and can become misleading even in the presence of one outlier, we provide a test which is resistant to outliers. The price to pay for robustness is a small loss of power, when the model holds exactly. | ^ checkRd: (-1) robfmtest.Rd:37: Lost braces; missing escapes or markup? 37 | Since the classical tests including {resettest}, {raintest} and {harvtest} implemented in {lmtest} are not resistant to outliers and can become misleading even in the presence of one outlier, we provide a test which is resistant to outliers. The price to pay for robustness is a small loss of power, when the model holds exactly. | ^ * 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 ... OK * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking examples ... [1s] OK * checking PDF version of manual ... [20s] OK * checking HTML version of manual ... [1s] OK * DONE Status: 1 NOTE