• using R Under development (unstable) (2012-05-22 r59405)
• using platform: x86_64-unknown-linux-gnu (64-bit)
• using session charset: UTF-8
• checking for file ‘fuzzyRankTests/DESCRIPTION’ ... OK
• this is package ‘fuzzyRankTests’ version ‘0.3-2’
• 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 executable files ... OK
• checking whether package ‘fuzzyRankTests’ can be installed ... OK
• checking installed package size ... OK
• 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 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 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 ... NOTE
  S3 methods shown with full name in documentation object 'fuzzyRankHelper':
  ‘plot.fuzzyrankci’ ‘plot.fuzzyranktest’ ‘print.fuzzyrankci’
  ‘print.fuzzyranktest’
  
  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 line endings in C/C++/Fortran sources/headers ... OK
• checking line endings in Makefiles ... OK
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking compiled code ... OK
• checking sizes of PDF files under ‘inst/doc’ ... OK
• checking installed files from ‘inst/doc’ ... NOTE
  The following files should probably not be installed:
  ‘design.tex’
  
  Consider the use of a .Rinstignore file: see ‘Writing R Extensions’,
  or move the vignette sources from ‘inst/doc’ to ‘vignettes’.
• checking examples ... OK
• checking for unstated dependencies in tests ... OK
• checking tests ... OK
  Running ‘ranksum.R’
  Comparing ‘ranksum.Rout’ to ‘ranksum.Rout.save’ ...103c103
  < -3.99995
  ---
  > -3.999972
  138c138
  < -3.99995
  ---
  > -3.999949
  173c173
  < -3.99995
  ---
  > -3.999996
  Running ‘sign-ci.R’
  Comparing ‘sign-ci.Rout’ to ‘sign-ci.Rout.save’ ... OK
  Running ‘sign.R’
  Comparing ‘sign.Rout’ to ‘sign.Rout.save’ ... OK
  Running ‘signrank.R’
  Comparing ‘signrank.Rout’ to ‘signrank.Rout.save’ ...158c158
  < 0.4999892 4.5000043
  ---
  > 0.4999542 4.5000543
  161c161
  < 2.500029
  ---
  > 2.500058
  202c202
  < 2.500029
  ---
  > 2.500003
  224,226c224,226
  < (-Inf, 0.5) 0.0000
  < {0.5} 0.9539
  < (0.5, Inf) 1.0000
  ---
  > (-Inf, 0.5) 0.000
  > {0.5} 0.954
  > (0.5, Inf) 1.000
  241c241
  < 2.500029
  ---
  > 2.500058
  Running ‘testc.R’
  Comparing ‘testc.Rout’ to ‘testc.Rout.save’ ...106c106
  < Incorrect number of arguments (4), expecting 5 for 'fpvranksum'
  ---
  > Incorrect number of arguments (4), expecting 5 for fpvranksum
  Running ‘testd.R’
  Comparing ‘testd.Rout’ to ‘testd.Rout.save’ ... OK
• checking PDF version of manual ... OK
  NOTE: There were 2 notes.
  See
  ‘/data/gannet/tmp/ripley/R/packages/tests-devel/fuzzyRankTests.Rcheck/00check.log’
  for details.