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 trio on zin2

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

Package 791/824HostnameOS / ArchINSTALLBUILDCHECKBUILD BIN
trio 3.2.1
Holger Schwender
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/trio
Last Changed Rev: 90047 / Revision: 95116
Last Changed Date: 2014-05-07 11:43:42 -0700 (Wed, 07 May 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: trio
Version: 3.2.1
Command: /home/biocbuild/bbs-2.14-bioc/R/bin/R CMD check --no-vignettes --timings trio_3.2.1.tar.gz
StartedAt: 2014-10-08 03:24:57 -0700 (Wed, 08 Oct 2014)
EndedAt: 2014-10-08 03:27:10 -0700 (Wed, 08 Oct 2014)
EllapsedTime: 133.9 seconds
RetCode: 0
Status:  OK 
CheckDir: trio.Rcheck
Warnings: 0

Command output

##############################################################################
##############################################################################
###
### Running command:
###
###   /home/biocbuild/bbs-2.14-bioc/R/bin/R CMD check --no-vignettes --timings trio_3.2.1.tar.gz
###
##############################################################################
##############################################################################


* using log directory ‘/home/biocbuild/bbs-2.14-bioc/meat/trio.Rcheck’
* using R version 3.1.1 (2014-07-10)
* using platform: x86_64-unknown-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘trio/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘trio’ version ‘3.2.1’
* 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 ‘trio’ can be installed ... [2s/2s] OK
* checking installed package size ... OK
* checking package directory ... OK
* checking ‘build’ directory ... 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
* 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 ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... NOTE
Foreign function call to a different package:
  .Fortran("slogreg", ..., PACKAGE = "LogicReg")
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 ... OK
* 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 installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [54s/54s] OK
Examples with CPU or elapsed time > 5s
               user system elapsed
print.trioFS  8.625  0.008   8.648
trioFS        8.609  0.004   8.627
trio.permTest 8.429  0.004   8.447
colGxGPerms   6.416  0.000   6.432
* 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 was 1 note.
See
  ‘/home/biocbuild/bbs-2.14-bioc/meat/trio.Rcheck/00check.log’
for details.

trio.Rcheck/00install.out:

* installing *source* package ‘trio’ ...
** 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 (trio)

trio.Rcheck/trio-Ex.timings:

nameusersystemelapsed
allelicTDT0.0320.0000.032
colEMlrt0.1440.0000.146
colGxE0.0120.0000.012
colGxGPerms6.4160.0006.432
colPOlrt0.0280.0000.029
colTDTmaxTest0.0920.0000.090
colTDTsam0.9000.0280.931
findLDblocks0.1040.0000.107
getLD0.0280.0000.030
getMatPseudo0.0120.0000.010
lrControl000
ped2geno0.0040.0000.001
plot.LDblocks0.0640.0040.069
plot.getLD0.1000.0000.097
plot.trioLR4.2240.0164.255
poly4root0.0000.0000.001
print.colGxE0.0800.0040.083
print.trioFS8.6250.0088.648
print.trioLR4.2080.0084.222
probTDT0.0680.0000.068
read.pedfile0.0000.0000.001
removeSNPs0.0080.0000.009
scoreTDT0.0160.0000.016
tdt0.0520.0000.052
tdtGxG1.7040.0041.711
trio.check1.1400.0041.145
trio.data0.0080.0000.007
trio.permTest8.4290.0048.447
trio.power0.0160.0000.018
trio.prepare4.0200.0004.029
trio.sim0.1800.0000.183
trioFS8.6090.0048.627
trioLR4.1840.0084.200