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 

BioC 2.14: CHECK report for flowTrans on petty

This page was generated on 2014-10-08 08:59:04 -0700 (Wed, 08 Oct 2014).

Package 294/824HostnameOS / ArchINSTALLBUILDCHECKBUILD BIN
flowTrans 1.16.0
Greg Finak
Snapshot Date: 2014-10-07 17:20:37 -0700 (Tue, 07 Oct 2014)
URL: https://hedgehog.fhcrc.org/bioconductor/branches/RELEASE_2_14/madman/Rpacks/flowTrans
Last Changed Rev: 88838 / Revision: 95116
Last Changed Date: 2014-04-11 14:07:21 -0700 (Fri, 11 Apr 2014)
zin2 Linux (Ubuntu 12.04.4 LTS) / x86_64  NotNeeded  OK  OK 
moscato2 Windows Server 2008 R2 Enterprise SP1 (64-bit) / x64  NotNeeded  OK  OK  OK 
petty Mac OS X Snow Leopard (10.6.8) / x86_64  NotNeeded  OK [ OK ] OK 
morelia Mac OS X Mavericks (10.9.5) / x86_64  NotNeeded  OK  OK  OK 

Summary

Package: flowTrans
Version: 1.16.0
Command: /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R CMD check --no-vignettes --timings --no-multiarch flowTrans_1.16.0.tar.gz
StartedAt: 2014-10-07 22:00:23 -0700 (Tue, 07 Oct 2014)
EndedAt: 2014-10-07 22:03:16 -0700 (Tue, 07 Oct 2014)
EllapsedTime: 173.3 seconds
RetCode: 0
Status:  OK 
CheckDir: flowTrans.Rcheck
Warnings: 0

Command output

##############################################################################
##############################################################################
###
### Running command:
###
###   /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R CMD check --no-vignettes --timings --no-multiarch flowTrans_1.16.0.tar.gz
###
##############################################################################
##############################################################################


* using log directory ‘/Users/biocbuild/bbs-2.14-bioc/meat/flowTrans.Rcheck’
* using R version 3.1.1 (2014-07-10)
* using platform: x86_64-apple-darwin10.8.0 (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘flowTrans/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘flowTrans’ version ‘1.16.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 ‘flowTrans’ can be installed ... [14s/14s] OK
* checking installed package size ... OK
* checking package directory ... OK
* checking ‘build’ directory ... OK
* checking DESCRIPTION meta-information ... NOTE
Packages listed in more than one of Depends, Imports, Suggests, Enhances:
  ‘flowCore’ ‘flowViz’ ‘flowClust’
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
There are ::: calls to the package's namespace in its code. A package
  almost never needs to use ::: for its own objects:
  ‘linlog’
See the information on DESCRIPTION files in the chapter ‘Creating R
packages’ of the ‘Writing R Extensions’ manual.
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... NOTE
Foreign function call to a different package:
  .Call("biexponential_transform", ..., PACKAGE = "flowCore")
See the chapter ‘System and foreign language interfaces’ of the
‘Writing R Extensions’ manual.
* 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 'summary.flowTransResult':
  ‘summary.flowTransResult’

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 sizes of PDF files under ‘inst/doc’ ... OK
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [21s/21s] OK
Examples with CPU or elapsed time > 5s
                   user system elapsed
flowTrans-package 8.472  0.233   8.878
* 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

NOTE: There were 4 notes.
See
  ‘/Users/biocbuild/bbs-2.14-bioc/meat/flowTrans.Rcheck/00check.log’
for details.

flowTrans.Rcheck/00install.out:

* installing *source* package ‘flowTrans’ ...
** R
** inst
** preparing package for lazy loading
** help
*** installing help indices
** building package indices
** installing vignettes
** testing if installed package can be loaded
* DONE (flowTrans)

flowTrans.Rcheck/flowTrans-Ex.timings:

nameusersystemelapsed
extractParams0.9650.0150.986
flowTrans-package8.4720.2338.878
flowTrans2.2570.1572.497
flowTransResult-class0.7120.0120.724
summary.flowTransResult0.6660.0010.668