############################################################################## ############################################################################## ### ### Running command: ### ### /Library/Frameworks/R.framework/Resources/bin/R CMD check --install=check:customProDB.install-out.txt --library=/Library/Frameworks/R.framework/Resources/library --no-vignettes --timings customProDB_1.40.0.tar.gz ### ############################################################################## ############################################################################## * using log directory ‘/Users/biocbuild/bbs-3.17-bioc/meat/customProDB.Rcheck’ * using R version 4.3.1 (2023-06-16) * using platform: x86_64-apple-darwin20 (64-bit) * R was compiled by Apple clang version 14.0.3 (clang-1403.0.22.14.1) GNU Fortran (GCC) 12.2.0 * running under: macOS Monterey 12.6.4 * using session charset: UTF-8 * using option ‘--no-vignettes’ * checking for file ‘customProDB/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘customProDB’ version ‘1.40.0’ * 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 ‘customProDB’ 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 R 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 dependencies in R code ... NOTE Unexported objects imported by ':::' calls: ‘biomaRt:::martBM’ ‘biomaRt:::martDataset’ ‘biomaRt:::martHost’ See the note in ?`:::` about the use of this operator. * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... NOTE Bed2Range: no visible binding for global variable ‘V5’ OutputNovelJun: no visible binding for global variable ‘jun_type’ OutputVarproseq: no visible binding for global variable ‘genename’ OutputVarproseq: no visible binding for global variable ‘txname’ OutputVarproseq: no visible binding for global variable ‘proname’ OutputVarproseq: no visible binding for global variable ‘aaref’ OutputVarproseq: no visible binding for global variable ‘aapos’ OutputVarproseq: no visible binding for global variable ‘aavar’ OutputVarproseq: no visible binding for global variable ‘rsid’ OutputVarproseq_single: no visible binding for global variable ‘genename’ OutputVarproseq_single: no visible binding for global variable ‘txname’ OutputVarproseq_single: no visible binding for global variable ‘proname’ OutputVarproseq_single: no visible binding for global variable ‘aaref’ OutputVarproseq_single: no visible binding for global variable ‘aapos’ OutputVarproseq_single: no visible binding for global variable ‘aavar’ OutputVarproseq_single: no visible binding for global variable ‘rsid’ Outputaberrant: no visible binding for global variable ‘pro_name’ Positionincoding: no visible binding for global variable ‘cds_start’ Positionincoding: no visible binding for global variable ‘cds_end’ PrepareAnnotationEnsembl: no visible binding for global variable ‘ensembl_gene_id’ PrepareAnnotationEnsembl: no visible binding for global variable ‘pro_name’ PrepareAnnotationEnsembl: no visible binding for global variable ‘chrom’ PrepareAnnotationEnsembl: no visible binding for global variable ‘name’ PrepareAnnotationEnsembl: no visible binding for global variable ‘alleleCount’ PrepareAnnotationEnsembl: no visible binding for global variable ‘alleles’ PrepareAnnotationRefseq: no visible binding for global variable ‘name’ PrepareAnnotationRefseq: no visible binding for global variable ‘mrnaAcc’ PrepareAnnotationRefseq: no visible binding for global variable ‘protAcc’ PrepareAnnotationRefseq: no visible binding for global variable ‘transcript’ PrepareAnnotationRefseq: no visible binding for global variable ‘chrom’ PrepareAnnotationRefseq: no visible binding for global variable ‘alleleCount’ PrepareAnnotationRefseq: no visible binding for global variable ‘alleles’ PrepareAnnotationRefseq: no visible binding for global variable ‘COSMIC’ Varlocation: no visible binding for global variable ‘pro_name’ Undefined global functions or variables: COSMIC V5 aapos aaref aavar alleleCount alleles cds_end cds_start chrom ensembl_gene_id genename jun_type mrnaAcc name pro_name proname protAcc rsid transcript txname * checking Rd files ... OK * 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 sizes of PDF files under ‘inst/doc’ ... OK * checking files in ‘vignettes’ ... OK * checking examples ... OK Examples with CPU (user + system) or elapsed time > 5s user system elapsed PrepareAnnotationEnsembl 8.421 0.497 29.909 easyRun_mul 6.446 0.140 8.376 OutputsharedPro 3.895 0.078 5.002 * checking for unstated dependencies in vignettes ... OK * checking package vignettes in ‘inst/doc’ ... OK * checking running R code from vignettes ... SKIPPED * checking re-building of vignette outputs ... SKIPPED * checking PDF version of manual ... OK * DONE Status: 2 NOTEs See ‘/Users/biocbuild/bbs-3.17-bioc/meat/customProDB.Rcheck/00check.log’ for details.