############################################################################## ############################################################################## ### ### Running command: ### ### /home/biocbuild/R/R/bin/R CMD check --install=check:ChAMP.install-out.txt --library=/home/biocbuild/R/R/site-library --no-vignettes --timings ChAMP_2.37.0.tar.gz ### ############################################################################## ############################################################################## * using log directory ‘/home/biocbuild/bbs-3.21-bioc/meat/ChAMP.Rcheck’ * using R Under development (unstable) (2024-11-24 r87369) * using platform: aarch64-unknown-linux-gnu * R was compiled by aarch64-unknown-linux-gnu-gcc (GCC) 14.2.0 GNU Fortran (GCC) 14.2.0 * running under: openEuler 24.03 (LTS) * using session charset: UTF-8 * using option ‘--no-vignettes’ * checking for file ‘ChAMP/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘ChAMP’ version ‘2.37.0’ * checking package namespace information ... OK * checking package dependencies ... INFO Depends: includes the non-default packages: 'minfi', 'ChAMPdata', 'DMRcate', 'Illumina450ProbeVariants.db', 'IlluminaHumanMethylationEPICmanifest', 'DT', 'RPMM' Adding so many packages to the search path is excessive and importing selectively is preferable. Imports includes 32 non-default packages. Importing from so many packages makes the package vulnerable to any of them becoming unavailable. Move as many as possible to Suggests and use conditionally. * 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 for sufficient/correct file permissions ... OK * checking whether package ‘ChAMP’ can be installed ... WARNING Found the following significant warnings: Warning: program compiled against libxml 212 using older 211 Note: possible error in 'dmrcate(myannotation, ': unused argument (mc.cores = cores) Warning: replacing previous import 'plyr::mutate' by 'plotly::mutate' when loading 'ChAMP' Warning: replacing previous import 'plyr::rename' by 'plotly::rename' when loading 'ChAMP' Warning: replacing previous import 'plyr::arrange' by 'plotly::arrange' when loading 'ChAMP' Warning: replacing previous import 'plyr::summarise' by 'plotly::summarise' when loading 'ChAMP' Warning: replacing previous import 'plotly::subplot' by 'Hmisc::subplot' when loading 'ChAMP' Warning: replacing previous import 'plyr::summarize' by 'Hmisc::summarize' when loading 'ChAMP' Warning: replacing previous import 'plyr::is.discrete' by 'Hmisc::is.discrete' when loading 'ChAMP' Warning: replacing previous import 'plotly::last_plot' by 'ggplot2::last_plot' when loading 'ChAMP' Warning: replacing previous import 'globaltest::model.matrix' by 'stats::model.matrix' when loading 'ChAMP' Warning: replacing previous import 'globaltest::p.adjust' by 'stats::p.adjust' when loading 'ChAMP' See ‘/home/biocbuild/bbs-3.21-bioc/meat/ChAMP.Rcheck/00install.out’ for details. Information on the location(s) of code generating the ‘Note’s can be obtained by re-running with environment variable R_KEEP_PKG_SOURCE set to ‘yes’. * checking installed package size ... OK * checking package directory ... OK * checking ‘build’ directory ... OK * checking DESCRIPTION meta-information ... NOTE Package listed in more than one of Depends, Imports, Suggests, Enhances: ‘rmarkdown’ A package should be listed in only one of these fields. * 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 ... 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 ... NOTE Warning: program compiled against libxml 212 using older 211 A namespace must be able to be loaded with just the base namespace loaded: otherwise if the namespace gets loaded by a saved object, the session will be unable to start. Probably some imports need to be declared in the NAMESPACE file. * checking whether the namespace can be unloaded cleanly ... OK * checking loading without being on the library search path ... OK * checking whether startup messages can be suppressed ... NOTE Warning: program compiled against libxml 212 using older 211 No methods found in package 'RSQLite' for request: 'dbListFields' when loading 'lumi' It looks like this package (or a package it requires) has a startup message which cannot be suppressed: see ?packageStartupMessage. * checking dependencies in R code ... NOTE Warning: program compiled against libxml 212 using older 211 Namespace in Imports field not imported from: 'prettydoc' All declared Imports should be used. Package in Depends field not imported from: 'DT' These packages need to be imported from (in the NAMESPACE file) for when this namespace is loaded but not attached. * checking S3 generic/method consistency ... WARNING Warning: program compiled against libxml 212 using older 211 See section ‘Generic functions and methods’ in the ‘Writing R Extensions’ manual. * checking replacement functions ... WARNING Warning: program compiled against libxml 212 using older 211 The argument of a replacement function which corresponds to the right hand side must be named ‘value’. * checking foreign function calls ... NOTE Warning: program compiled against libxml 212 using older 211 See chapter ‘System and foreign language interfaces’ in the ‘Writing R Extensions’ manual. * checking R code for possible problems ... NOTE Warning: program compiled against libxml 212 using older 211 champ.DMR: possible error in dmrcate(myannotation, min.cpgs = minProbes, lambda = lambda, C = C, mc.cores = cores): unused argument (mc.cores = cores) champ.ebGSEA : gseaWTfn: no visible global function definition for 'wilcox.test' champ.ebGSEA: no visible global function definition for 'stopCluster' champ.norm: no visible global function definition for 'stopCluster' champ.process: no visible global function definition for 'champ.EpiMod' Undefined global functions or variables: champ.EpiMod stopCluster wilcox.test Consider adding importFrom("stats", "wilcox.test") to your NAMESPACE file. * checking Rd files ... OK * checking Rd metadata ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... WARNING Warning: program compiled against libxml 212 using older 211 All user-level objects in a package should have documentation entries. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual. * checking for code/documentation mismatches ... WARNING Warning: program compiled against libxml 212 using older 211 Warning: program compiled against libxml 212 using older 211 Warning: program compiled against libxml 212 using older 211 * checking Rd \usage sections ... WARNING Duplicated \argument entries in Rd file 'champ.SVD.Rd': ‘Rplot’ 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. Warning: program compiled against libxml 212 using older 211 The \usage entries for S3 methods should use the \method markup and not their full name. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual. * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking files in ‘vignettes’ ... OK * checking examples ... OK * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking running R code from vignettes ... SKIPPED * checking re-building of vignette outputs ... SKIPPED * checking PDF version of manual ... OK * DONE Status: 6 WARNINGs, 6 NOTEs See ‘/home/biocbuild/bbs-3.21-bioc/meat/ChAMP.Rcheck/00check.log’ for details.