BayesPeak 1.21.0
Jonathan Cairns
| Snapshot Date: 2015-08-23 16:24:14 -0700 (Sun, 23 Aug 2015) | | URL: https://hedgehog.fhcrc.org/bioconductor/trunk/madman/Rpacks/BayesPeak | | Last Changed Rev: 102594 / Revision: 107696 | | Last Changed Date: 2015-04-16 13:02:44 -0700 (Thu, 16 Apr 2015) |
| zin1 | Linux (Ubuntu 14.04.2 LTS) / x86_64 | NotNeeded | OK | [ OK ] | |  |
| perceval | Mac OS X Snow Leopard (10.6.8) / x86_64 | NotNeeded | OK | OK | OK | |
| oaxaca | Mac OS X Mavericks (10.9.5) / x86_64 | NotNeeded | OK | OK | OK | |
##############################################################################
##############################################################################
###
### Running command:
###
### /home/biocbuild/bbs-3.2-bioc/R/bin/R CMD check --no-vignettes --timings BayesPeak_1.21.0.tar.gz
###
##############################################################################
##############################################################################
* using log directory ‘/home/biocbuild/bbs-3.2-bioc/meat/BayesPeak.Rcheck’
* using R version 3.2.2 (2015-08-14)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘BayesPeak/DESCRIPTION’ ... OK
* this is package ‘BayesPeak’ version ‘1.21.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 ... [5s/5s] OK
* checking installed package size ... NOTE
installed size is 6.7Mb
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 loading without being on the library search path ... 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 ... 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 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
File ‘BayesPeak/libs/BayesPeak.so’:
Found ‘stdout’, possibly from ‘stdout’ (C)
Object: ‘bayespeak.o’
Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor the system RNG.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
* checking sizes of PDF files under ‘inst/doc’ ... OK
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [264s/268s] OK
Examples with CPU or elapsed time > 5s
user system elapsed
summarise.peaks 128.661 0.04 132.017
bayespeak 128.032 0.02 128.258
* 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: 5 NOTEs
See
‘/home/biocbuild/bbs-3.2-bioc/meat/BayesPeak.Rcheck/00check.log’
for details.
* installing *source* package ‘BayesPeak’ ...
** libs
gcc -std=gnu99 -I/home/biocbuild/bbs-3.2-bioc/R/include -DNDEBUG -I/usr/local/include -fpic -g -O2 -Wall -c bayespeak.c -o bayespeak.o
bayespeak.c: In function ‘bayespeak’:
bayespeak.c:176:27: warning: variable ‘M’ set but not used [-Wunused-but-set-variable]
double M1, M2, M3, M4, M, a, b;
^
gcc -std=gnu99 -shared -L/home/biocbuild/bbs-3.2-bioc/R/lib -L/usr/local/lib -o BayesPeak.so bayespeak.o -L/home/biocbuild/bbs-3.2-bioc/R/lib -lR
installing to /home/biocbuild/bbs-3.2-bioc/meat/BayesPeak.Rcheck/BayesPeak/libs
** R
** data
** inst
** preparing package for lazy loading
** help
*** installing help indices
** building package indices
** installing vignettes
** testing if installed package can be loaded
* DONE (BayesPeak)