############################################################################## ############################################################################## ### ### Running command: ### ### /home/biocbuild/R/R/bin/R CMD check --install=check:memes.install-out.txt --library=/home/biocbuild/R/R/site-library --no-vignettes --timings memes_1.14.0.tar.gz ### ############################################################################## ############################################################################## * using log directory ‘/home/biocbuild/bbs-3.20-bioc/meat/memes.Rcheck’ * using R version 4.4.1 (2024-06-14) * using platform: aarch64-unknown-linux-gnu * R was compiled by gcc (GCC) 12.2.1 20220819 (openEuler 12.2.1-14) GNU Fortran (GCC) 10.3.1 * running under: openEuler 22.03 (LTS-SP1) * using session charset: UTF-8 * using option ‘--no-vignettes’ * checking for file ‘memes/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘memes’ version ‘1.14.0’ * 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 hidden files and directories ... OK * checking for portable file names ... OK * checking for sufficient/correct file permissions ... OK * checking whether package ‘memes’ can be installed ... OK * checking installed package size ... OK * 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 ... 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 dependencies in R code ... OK * checking S3 generic/method consistency ... WARNING motif_input: function(x, ...) motif_input.universalmotif_df: function(input, path) motif_input: function(x, ...) motif_input.universalmotif: function(input, path) motif_input: function(x, ...) motif_input.list: function(input, path) motif_input: function(x, ...) motif_input.character: function(input, path) motif_input: function(x, ...) motif_input.data.frame: function(input, path) sequence_input: function(x) sequence_input.DNAStringSet: function(input) sequence_input: function(x) sequence_input.character: function(input) sequence_input: function(x) sequence_input.BStringSet: function(input) sequence_input: function(x) sequence_input.AAStringSet: function(input) See section ‘Generic functions and methods’ in the ‘Writing R Extensions’ manual. * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... OK * checking Rd files ... NOTE checkRd: (-1) runTomTom.Rd:51: Lost braces; missing escapes or markup? 51 | \item{...}{additional flags passed to tomtom using {cmdfun} formating (see table below for details)} | ^ * 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 contents of ‘data’ directory ... OK * checking data for non-ASCII characters ... OK * checking LazyData ... OK * checking data for ASCII and uncompressed saves ... OK * checking files in ‘vignettes’ ... OK * checking examples ... ERROR Running examples in ‘memes-Ex.R’ failed The error most likely occurred in: > base::assign(".ptime", proc.time(), pos = "CheckExEnv") > ### Name: runMeme > ### Title: Identify motifs with MEME > ### Aliases: runMeme runMeme.list runMeme.BStringSetList runMeme.default > > ### ** Examples > > if (meme_is_installed()) { + seqs <- universalmotif::create_sequences("CCRAAAW", seqnum = 4) + names(seqs) <- 1:length(seqs) + runMeme(seqs, parse_genomic_coord = FALSE) + + } [kunpeng2:1412861] mca_base_component_repository_open: unable to open mca_pmix_ext3x: /usr/lib64/openmpi/lib/openmpi/mca_pmix_ext3x.so: undefined symbol: pmix_value_load (ignored) [kunpeng2:1412861] [[6907,0],0] ORTE_ERROR_LOG: Not found in file ess_hnp_module.c at line 320 -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): opal_pmix_base_select failed --> Returned value Not found (-13) instead of ORTE_SUCCESS -------------------------------------------------------------------------- [kunpeng2:1412853] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file ess_singleton_module.c at line 716 [kunpeng2:1412853] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file ess_singleton_module.c at line 172 -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_ess_init failed --> Returned value Unable to start a daemon on the local node (-127) instead of ORTE_SUCCESS -------------------------------------------------------------------------- -------------------------------------------------------------------------- It looks like MPI_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): ompi_mpi_init: ompi_rte_init failed --> Returned "Unable to start a daemon on the local node" (-127) instead of "Success" (0) -------------------------------------------------------------------------- *** An error occurred in MPI_Init *** on a NULL communicator *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, *** and potentially your MPI job) [kunpeng2:1412853] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! Error: Invalid flags. Did you mean: ">" instead of: "oc" ">" instead of: "dna" Execution halted * 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: 1 ERROR, 1 WARNING, 1 NOTE See ‘/home/biocbuild/bbs-3.20-bioc/meat/memes.Rcheck/00check.log’ for details.