Back to the "Multiple platform build/check report" A [B] C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z 

Package 47/514HostnameOS / ArchBUILDCHECKBUILD BIN
BayesPeak 1.6.0
Jonathan Cairns
Snapshot Date: 2012-03-23 18:21:46 -0700 (Fri, 23 Mar 2012)
URL: https://hedgehog.fhcrc.org/bioconductor/branches/RELEASE_2_9/madman/Rpacks/BayesPeak
Last Changed Rev: 59920 / Revision: 64395
Last Changed Date: 2011-10-31 15:59:03 -0700 (Mon, 31 Oct 2011)
wilson2 Linux (openSUSE 11.4) / x86_64  OK [ OK ]
moscato1 Windows Server 2008 R2 Enterprise SP1 (64-bit) / x64  OK  OK  OK 
pitt Mac OS X Leopard (10.5.8) / i386  OK  OK  OK 

Summary

Package: BayesPeak
Version: 1.6.0
Command: /home/biocbuild/bbs-2.9-bioc/R/bin/R CMD check --no-vignettes --timings BayesPeak_1.6.0.tar.gz
StartedAt: 2012-03-23 23:16:37 -0700 (Fri, 23 Mar 2012)
EndedAt: 2012-03-23 23:22:32 -0700 (Fri, 23 Mar 2012)
EllapsedTime: 355.8 seconds
RetCode: 0
Status:  OK 
CheckDir: BayesPeak.Rcheck
Warnings: 0

Command output

* using log directory ‘/loc/home/biocbuild/bbs-2.9-bioc/meat/BayesPeak.Rcheck’
* using R version 2.14.2 (2012-02-29)
* using platform: x86_64-unknown-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.6.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 whether package ‘BayesPeak’ can be installed ... OK
* checking installed package size ... NOTE
  installed size is  6.9Mb
  sub-directories of 1Mb or more:
    data      1.2Mb
    extdata   5.0Mb
* checking package directory ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level 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 for unstated dependencies in R code ... OK
* 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 the 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 ... NOTE
  
  Note: significantly better compression could be obtained
        by using R CMD build --resave-data
                         old_size new_size compress
  raw.output.H3K4me3.rda     76Kb     66Kb       xz
  raw.output.rda            1.1Mb    978Kb       xz
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking line endings in Makefiles ... OK
* checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
* checking compiled code ... NOTE
File ‘/loc/home/biocbuild/bbs-2.9-bioc/meat/BayesPeak.Rcheck/BayesPeak/libs/BayesPeak.so’:
  Found ‘stdout’, possibly from ‘stdout’ (C)

Compiled code should not call functions which might terminate R nor
write to stdout/stderr instead of to the console.  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 examples ... OK
* 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 vignettes ... SKIPPED
* checking PDF version of manual ... OK

BayesPeak.Rcheck/00install.out:

* installing *source* package ‘BayesPeak’ ...
** libs
gcc -std=gnu99 -I/home/biocbuild/bbs-2.9-bioc/R/include  -I/usr/local/include    -fpic  -g -O2 -c bayespeak.c -o bayespeak.o
gcc -std=gnu99 -shared -L/usr/local/lib64 -o BayesPeak.so bayespeak.o -L/home/biocbuild/bbs-2.9-bioc/R/lib -lR
installing to /loc/home/biocbuild/bbs-2.9-bioc/meat/BayesPeak.Rcheck/BayesPeak/libs
** R
** data
** inst
** preparing package for lazy loading
** help
*** installing help indices
** building package indices ...
*** tangling vignette sources ...
   ‘BayesPeak.Rnw’ 
** testing if installed package can be loaded

* DONE (BayesPeak)

BayesPeak.Rcheck/BayesPeak-Ex.timings:

nameusersystemelapsed
bayespeak138.900 0.052140.905
overfitting0.0760.0000.078
plot.PP0.0520.0040.058
plot.bed1.1040.0121.116
plot.job8.7170.0729.151
read.bed0.9120.0040.935
summarise.peaks138.689 0.124141.256