AffymetrixDataTestFiles 0.1.2 Henrik Bengtsson
Snapshot Date: 2011-07-01 11:15:06 -0700 (Fri, 01 Jul 2011) | URL: https://hedgehog.fhcrc.org/bioc-data/trunk/experiment/pkgs/AffymetrixDataTestFiles | Last Changed Rev: 959 / Revision: 1675 | Last Changed Date: 2009-09-10 11:19:18 -0700 (Thu, 10 Sep 2009) |
| wilson2 | Linux (openSUSE 11.4) / x86_64 | OK | OK | |
liverpool | Windows Server 2003 R2 (32-bit) / x64 | OK | OK | OK |
petty | Mac OS X Snow Leopard (10.6.7) / i386 | OK | [ OK ] | OK |
* using log directory '/Users/biocbuild/bbs-2.9-data-experiment/meat/AffymetrixDataTestFiles.Rcheck'
* using R version 2.14.0 Under development (unstable) (2011-04-24 r55634)
* using platform: i386-apple-darwin9.8.0 (32-bit)
* using session charset: ASCII
* using option '--no-vignettes'
* checking for file 'AffymetrixDataTestFiles/DESCRIPTION' ... OK
* this is package 'AffymetrixDataTestFiles' version '0.1.2'
* checking package name space information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking whether package 'AffymetrixDataTestFiles' can be installed ... OK
* checking installed package size ... NOTE
installed size is 147.3Mb
sub-directories of 1Mb or more:
annotationData 70.7Mb
gcos11Data 49.4Mb
gcos14Data 6.7Mb
rawData 20.5Mb
* 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 name space can be loaded with stated dependencies ... OK
* checking whether the name space 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 ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking examples ... NONE
* checking PDF version of manual ... OK