Back to Multiple platform build/check report for BioC 3.6
ABCDE[F]GHIJKLMNOPQRSTUVWXYZ

CHECK report for flowTrans on veracruz1

This page was generated on 2018-04-12 13:33:42 -0400 (Thu, 12 Apr 2018).

Package 495/1472HostnameOS / ArchINSTALLBUILDCHECKBUILD BIN
flowTrans 1.30.0
Greg Finak
Snapshot Date: 2018-04-11 16:45:18 -0400 (Wed, 11 Apr 2018)
URL: https://git.bioconductor.org/packages/flowTrans
Branch: RELEASE_3_6
Last Commit: 3c0081e
Last Changed Date: 2017-10-30 12:39:29 -0400 (Mon, 30 Oct 2017)
malbec1 Linux (Ubuntu 16.04.1 LTS) / x86_64  NotNeeded  OK  OK UNNEEDED, same version exists in internal repository
tokay1 Windows Server 2012 R2 Standard / x64  NotNeeded  OK  OK  OK UNNEEDED, same version exists in internal repository
veracruz1 OS X 10.11.6 El Capitan / x86_64  NotNeeded  OK [ OK ] OK UNNEEDED, same version exists in internal repository

Summary

Package: flowTrans
Version: 1.30.0
Command: /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R CMD check --no-vignettes --timings flowTrans_1.30.0.tar.gz
StartedAt: 2018-04-12 03:50:40 -0400 (Thu, 12 Apr 2018)
EndedAt: 2018-04-12 03:52:19 -0400 (Thu, 12 Apr 2018)
EllapsedTime: 99.4 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 flowTrans_1.30.0.tar.gz
###
##############################################################################
##############################################################################


* using log directory ‘/Users/biocbuild/bbs-3.6-bioc/meat/flowTrans.Rcheck’
* using R version 3.4.4 (2018-03-15)
* using platform: x86_64-apple-darwin15.6.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.30.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 ... 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
Unexported object imported by a ':::' call: ‘flowCore:::biexponential_transform’
  See the note in ?`:::` about the use of this operator.
There are ::: calls to the package's namespace in its code. A package
  almost never needs to use ::: for its own objects:
  ‘linlog’
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... NOTE
Foreign function call to a different package:
  .Call("flowCore_biexponential_transform", ..., PACKAGE = "flowCore")
See chapter ‘System and foreign language interfaces’ in 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 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 ... 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 vignette outputs ... SKIPPED
* checking PDF version of manual ... OK
* DONE

Status: 4 NOTEs
See
  ‘/Users/biocbuild/bbs-3.6-bioc/meat/flowTrans.Rcheck/00check.log’
for details.



Installation output

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)

Tests output


Example timings

flowTrans.Rcheck/flowTrans-Ex.timings

nameusersystemelapsed
extractParams0.5550.0130.571
flowTrans-package3.8490.1514.055
flowTrans1.1560.0641.233
flowTransResult-class0.2130.0020.216
summary.flowTransResult0.2500.0050.256