Multiple platform build/check report for BioC 3.9 - CHECK report for BayesPeak on merida2

##############################################################################
##############################################################################
###
### Running command:
###
###   /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R CMD check --install=check:BayesPeak.install-out.txt --library=/Library/Frameworks/R.framework/Versions/Current/Resources/library --no-vignettes --timings BayesPeak_1.35.0.tar.gz
###
##############################################################################
##############################################################################


* using log directory ‘/Users/biocbuild/bbs-3.9-bioc/meat/BayesPeak.Rcheck’
* using R Under development (unstable) (2018-11-27 r75683)
* using platform: x86_64-apple-darwin15.6.0 (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘BayesPeak/DESCRIPTION’ ... OK
* this is package ‘BayesPeak’ version ‘1.35.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 ‘BayesPeak’ can be installed ... OK
* checking installed package size ... NOTE
  installed size is  6.3Mb
  sub-directories of 1Mb or more:
    data      1.0Mb
    extdata   5.0Mb
* checking package directory ... OK
* checking ‘build’ directory ... OK
* checking DESCRIPTION meta-information ... NOTE
Package listed in more than one of Depends, Imports, Suggests, Enhances:
  ‘IRanges’
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 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
'library' or 'require' call to ‘parallel’ in package code.
  Please use :: or requireNamespace() instead.
  See section 'Suggested packages' in the 'Writing R Extensions' manual.
* checking S3 generic/method consistency ... NOTE
Found the following apparent S3 methods exported but not registered:
  identify.overfitdiag plot.PP plot.bed plot.job plot.overfitdiag
See section ‘Registering S3 methods’ in the ‘Writing R Extensions’
manual.
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... NOTE
identify.overfitdiag: no visible global function definition for
  ‘identify’
plot.job: no visible global function definition for ‘plot’
plot.overfitdiag: no visible global function definition for ‘plot’
region.overfitdiag: no visible global function definition for ‘locator’
region.overfitdiag: no visible global function definition for ‘polygon’
Undefined global functions or variables:
  identify locator plot polygon
Consider adding
  importFrom("graphics", "identify", "locator", "plot", "polygon")
to your NAMESPACE file.
* 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 ... NOTE
S3 methods shown with full name in documentation object 'overfittingDiagnostics':
  ‘plot.overfitdiag’ ‘identify.overfitdiag’

S3 methods shown with full name in documentation object 'plot.PP':
  ‘plot.PP’

S3 methods shown with full name in documentation object 'plot.bed':
  ‘plot.bed’

S3 methods shown with full name in documentation object 'plot.job':
  ‘plot.job’

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 contents of ‘data’ directory ... OK
* checking data for non-ASCII characters ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking compiled code ... NOTE
Note: information on .o files is not available
File ‘/Library/Frameworks/R.framework/Versions/3.6/Resources/library/BayesPeak/libs/BayesPeak.so’:
  Found ‘___stdoutp’, possibly from ‘stdout’ (C)

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs. The detected symbols are linked into the code but
might come from libraries and not actually be called.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
* checking sizes of PDF files under ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... OK
Examples with CPU or elapsed time > 5s
                  user system elapsed
summarise.peaks 57.438  0.151  58.038
bayespeak       57.062  0.158  57.709
plot.job         6.034  0.215   6.298
* 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: 7 NOTEs
See
  ‘/Users/biocbuild/bbs-3.9-bioc/meat/BayesPeak.Rcheck/00check.log’
for details.

##############################################################################
##############################################################################
###
### Running command:
###
###   /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R CMD INSTALL BayesPeak
###
##############################################################################
##############################################################################


* installing to library ‘/Library/Frameworks/R.framework/Versions/3.6/Resources/library’
* installing *source* package ‘BayesPeak’ ...
** libs
clang -I"/Library/Frameworks/R.framework/Resources/include" -DNDEBUG   -I/usr/local/include   -fPIC  -Wall -g -O2  -c bayespeak.c -o bayespeak.o
clang -dynamiclib -Wl,-headerpad_max_install_names -undefined dynamic_lookup -single_module -multiply_defined suppress -L/Library/Frameworks/R.framework/Resources/lib -L/usr/local/lib -o BayesPeak.so bayespeak.o -F/Library/Frameworks/R.framework/.. -framework R -Wl,-framework -Wl,CoreFoundation
installing to /Library/Frameworks/R.framework/Versions/3.6/Resources/library/BayesPeak/libs
** R
** data
** inst
** byte-compile and prepare package for lazy loading
** help
*** installing help indices
** building package indices
** installing vignettes
** testing if installed package can be loaded
* DONE (BayesPeak)

CHECK report for BayesPeak on merida2

Summary

Command output

Installation output

Tests output

Example timings

name	user	system	elapsed
bayespeak	57.062	0.158	57.709
overfitting	0.158	0.011	0.173
plot.PP	0.120	0.004	0.130
plot.bed	0.825	0.027	0.859
plot.job	6.034	0.215	6.298
read.bed	1.126	0.018	1.153
summarise.peaks	57.438	0.151	58.038