R Development Page

ROI.tests log file (check_x86_64_linux)

Tue Jan 22 15:36:29 2019: Checking package ROI.tests (SVN revision 576) ...
* using log directory ‘/srv/rf/building/build_2019-01-22-15-27/RF_PKG_CHECK/PKGS/ROI.tests.Rcheck’
* using R version 3.5.2 Patched (2019-01-14 r75992)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--as-cran’
* checking for file ‘ROI.tests/DESCRIPTION’ ... OK
* this is package ‘ROI.tests’ version ‘0.0-2’
* checking CRAN incoming feasibility ... NOTE
Maintainer: ‘Florian Schwendinger ’

New submission

The Description field should not start with the package name,
  'This package' or similar.
* 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 for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking serialization versions ... OK
* checking whether package ‘ROI.tests’ can be installed ... [2s/2s] OK
* checking installed package size ... OK
* checking package directory ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... NOTE
Non-standard file/directory found at top level:
* 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 use of S3 registration ... OK
* checking dependencies in R code ... NOTE
Unexported object imported by a ':::' call: ‘ROI:::get_solver_methods’
  See the note in ?`:::` about the use of this operator.
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [5s/5s] OK
* checking for missing documentation entries ... WARNING
Undocumented code objects:
  ‘SOLVER_TESTS’ ‘TESTS’ ‘blue’ ‘check’ ‘check_bounds’ ‘correct_types’
  ‘cyan’ ‘error’ ‘get_test’ ‘green’ ‘info’ ‘magenta’ ‘mksig’
  ‘needs_start_value’ ‘new_solver_test’ ‘new_test’ ‘note’ ‘red’
  ‘register_solver_test’ ‘register_test’ ‘solver_control’ ‘test_cp_01’
  ‘test_cp_02’ ‘test_cp_03’ ‘test_cp_04’ ‘test_cp_05’ ‘test_cp_06’
  ‘test_cp_07’ ‘test_cp_08’ ‘test_cp_09’ ‘test_lp_01’ ‘test_lp_02’
  ‘test_lp_03’ ‘test_milp_01’ ‘test_milp_02’ ‘test_nlp_01’
  ‘test_nlp_02’ ‘test_nlp_03’ ‘test_nlp_04’ ‘test_nlp_05’ ‘test_nlp_06’
  ‘test_qcqp_01’ ‘test_qp_01’ ‘test_qp_02’ ‘test_solver’ ‘warn’
All user-level objects in a package should have documentation entries.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking examples ... NONE
* checking PDF version of manual ... OK
* checking for code which exercises the package ... WARNING
No examples, no tests, no vignettes

Status: 2 WARNINGs, 3 NOTEs
for details.

Run time: 40.79 seconds.

Additional Logs:   00install.out
Thanks to:
Vienna University of Economics and Business Powered By FusionForge