* using log directory 'd:/RCompile/CRANincoming/R-devel/mediationFlow.Rcheck' * using R Under development (unstable) (2025-04-29 r88182 ucrt) * using platform: x86_64-w64-mingw32 * R was compiled by gcc.exe (GCC) 14.2.0 GNU Fortran (GCC) 14.2.0 * running under: Windows Server 2022 x64 (build 20348) * using session charset: UTF-8 * checking for file 'mediationFlow/DESCRIPTION' ... OK * this is package 'mediationFlow' version '0.1.0' * package encoding: UTF-8 * checking CRAN incoming feasibility ... NOTE Maintainer: 'jarrett zhang ' New submission License components with restrictions and base license permitting such: MIT + file LICENSE Package has a VignetteBuilder field but no prebuilt vignette index. * checking package namespace information ... OK * checking package dependencies ... INFO Vignette dependency required without any vignettes: 'knitr' * 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 serialization versions ... OK * checking whether package 'mediationFlow' can be installed ... OK * checking installed package size ... OK * checking package directory ... OK * checking for future file timestamps ... OK * checking DESCRIPTION meta-information ... WARNING Invalid license file pointers: LICENSE * checking top-level files ... NOTE Non-standard files/directories found at top level: 'mediationFlow.Rproj' 'multiple_process_results.xlsx' 'single_process_result.xlsx' * checking for left-over files ... OK * checking index information ... OK * checking package subdirectories ... OK * checking code files for non-ASCII characters ... WARNING Found the following file with non-ASCII characters: R/save_process_results.R Portable packages must use only ASCII characters in their R code and NAMESPACE directives, except perhaps in comments. Use \uxxxx escapes for other characters. Function 'tools::showNonASCIIfile' can help in finding non-ASCII characters in files. * checking R files for syntax errors ... OK * checking whether the package can be loaded ... OK * checking whether the package can be loaded with stated dependencies ... OK * checking whether the package can be unloaded cleanly ... OK * checking whether the namespace can be loaded with stated dependencies ... OK * checking whether the namespace can be unloaded cleanly ... OK * checking loading without being on the library search path ... OK * checking use of S3 registration ... OK * checking dependencies in R code ... WARNING 'library' or 'require' call not declared from: 'openxlsx' 'library' or 'require' call to 'openxlsx' in package code. Please use :: or requireNamespace() instead. See section 'Suggested packages' in the 'Writing R Extensions' manual. * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... OK * checking Rd files ... OK * 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 ... WARNING Undocumented arguments in Rd file 'save_process_results.Rd' 'file_name' Documented arguments not in \usage in Rd file 'save_process_results.Rd': 'file_path' 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 examples ... OK * checking for unstated dependencies in 'tests' ... OK * checking tests ... OK Running 'testthat.R' * checking PDF version of manual ... [21s] OK * checking HTML version of manual ... OK * DONE Status: 4 WARNINGs, 2 NOTEs