SCM

R Development Page

ursa log file (check_x86_64_linux)

Mon Jan  7 09:12:04 2019: Checking package ursa (SVN revision 82) ...
* using log directory ‘/srv/rf/building/build_2019-01-07-09-08/RF_PKG_CHECK/PKGS/ursa.Rcheck’
* using R version 3.5.2 Patched (2019-01-02 r75945)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--as-cran’
* checking for file ‘ursa/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘ursa’ version ‘3.8.13’
* checking CRAN incoming feasibility ... NOTE
Maintainer: ‘Nikita Platonov ’

New submission

Package was archived on CRAN

CRAN repository db overrides:
  X-CRAN-Comment: Archived on 2018-06-10 for policy violation.

  Leaves behind directory in /tmp Also has memory-access errors
    reported by ASAN.
* 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 ‘ursa’ can be installed ... [5s/5s] OK
* checking installed package size ... OK
* checking package 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 use of S3 registration ... OK
* checking 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 ... [57s/57s] OK
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... NOTE
Packages unavailable to check Rd xrefs: ‘rje’, ‘magick’
* 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 line endings in C/C++/Fortran sources/headers ... OK
* checking pragmas in C/C++ headers and code ... OK
* checking compilation flags used ... OK
* checking compiled code ... OK
* checking examples ... [180s/181s] NOTE
Examples with CPU or elapsed time > 5s
               user system elapsed
panel_raster  5.008  0.304   5.301
panel_shading 4.641  0.459   5.083
compose_open  4.373  0.724   5.098
** found \donttest examples: check also with --run-donttest
* checking PDF version of manual ... OK
* DONE

Status: 3 NOTEs
See
  ‘/srv/rf/building/build_2019-01-07-09-08/RF_PKG_CHECK/PKGS/ursa.Rcheck/00check.log’
for details.


Run time: 306.59 seconds.

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