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 211/609HostnameOS / ArchBUILDCHECKBUILD BIN
flowTrans 1.10.0
Greg Finak
Snapshot Date: 2013-03-24 16:21:20 -0700 (Sun, 24 Mar 2013)
URL: https://hedgehog.fhcrc.org/bioconductor/branches/RELEASE_2_11/madman/Rpacks/flowTrans
Last Changed Rev: 70050 / Revision: 74773
Last Changed Date: 2012-10-01 15:16:24 -0700 (Mon, 01 Oct 2012)
lamb1 Linux (openSUSE 12.1) / x86_64  OK  OK 
moscato1 Windows Server 2008 R2 Enterprise SP1 (64-bit) / x64  OK [ OK ] OK 
perceval Mac OS X Leopard (10.5.8) / i386  OK  OK  OK 

Summary

Package: flowTrans
Version: 1.10.0
Command: rm -rf flowTrans.buildbin-libdir && mkdir flowTrans.buildbin-libdir && D:\biocbld\bbs-2.11-bioc\R\bin\R.exe CMD INSTALL --build --merge-multiarch --library=flowTrans.buildbin-libdir flowTrans_1.10.0.tar.gz >flowTrans-install.out 2>&1 && D:\biocbld\bbs-2.11-bioc\R\bin\R.exe CMD check --library=flowTrans.buildbin-libdir --install="check:flowTrans-install.out" --force-multiarch --no-vignettes --timings flowTrans_1.10.0.tar.gz && mv flowTrans.buildbin-libdir/* flowTrans.Rcheck/ && rmdir flowTrans.buildbin-libdir
StartedAt: 2013-03-25 00:57:43 -0700 (Mon, 25 Mar 2013)
EndedAt: 2013-03-25 00:59:43 -0700 (Mon, 25 Mar 2013)
EllapsedTime: 119.9 seconds
RetCode: 0
Status:  OK  
CheckDir: flowTrans.Rcheck
Warnings: 0

Command output

* using log directory 'D:/biocbld/bbs-2.11-bioc/meat/flowTrans.Rcheck'
* using R version 2.15.3 (2013-03-01)
* using platform: i386-w64-mingw32 (32-bit)
* using session charset: ISO8859-1
* using option '--no-vignettes'
* checking for file 'flowTrans/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'flowTrans' version '1.10.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 'flowTrans' can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking for portable file names ... OK
* checking DESCRIPTION meta-information ... OK
* 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
* loading checks for arch 'i386'
** 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
* loading checks for arch 'x64'
** 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 ... NOTE
Foreign function call with 'PACKAGE' argument in 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 installed files from 'inst/doc' ... OK
* checking examples ...
** running examples for arch 'i386' ... OK
Examples with CPU or elapsed time > 5s
                  user system elapsed
flowTrans-package 5.05   0.04    5.09
** running examples for arch 'x64' ... OK
Examples with CPU or elapsed time > 5s
                  user system elapsed
flowTrans-package 5.29   0.04    5.46
* 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

NOTE: There were 2 notes.
See
  'D:/biocbld/bbs-2.11-bioc/meat/flowTrans.Rcheck/00check.log'
for details.

flowTrans.Rcheck/00install.out:


install for i386

* installing *source* package 'flowTrans' ...
** R
** inst
** preparing package for lazy loading
** help
*** installing help indices
** building package indices
** installing vignettes
   'flowTrans.Rnw' 
** testing if installed package can be loaded

install for x64

* installing *source* package 'flowTrans' ...
** testing if installed package can be loaded
* MD5 sums
packaged installation of 'flowTrans' as flowTrans_1.10.0.zip

* DONE (flowTrans)