Multiple platform build/check report for BioC 3.8 - CHECK report for NuPoP on malbec1

##############################################################################
##############################################################################
###
### Running command:
###
###   /home/biocbuild/bbs-3.8-bioc/R/bin/R CMD check --install=check:NuPoP.install-out.txt --library=/home/biocbuild/bbs-3.8-bioc/R/library --no-vignettes --timings NuPoP_1.32.0.tar.gz
###
##############################################################################
##############################################################################


* using log directory ‘/home/biocbuild/bbs-3.8-bioc/meat/NuPoP.Rcheck’
* using R version 3.5.3 (2019-03-11)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘NuPoP/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘NuPoP’ version ‘1.32.0’
* 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 ‘NuPoP’ can be installed ... OK
* checking installed package size ... NOTE
  installed size is  6.0Mb
  sub-directories of 1Mb or more:
    extdata   4.9Mb
* 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 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 ... NOTE
plotNuPoP: no visible global function definition for ‘par’
plotNuPoP: no visible global function definition for ‘plot’
plotNuPoP: no visible global function definition for ‘title’
plotNuPoP: no visible global function definition for ‘polygon’
plotNuPoP: no visible global function definition for ‘points’
readNuPoP: no visible global function definition for ‘read.table’
Undefined global functions or variables:
  par plot points polygon read.table title
Consider adding
  importFrom("graphics", "par", "plot", "points", "polygon", "title")
  importFrom("utils", "read.table")
to your NAMESPACE file.
* 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 R/sysdata.rda ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking compiled code ... NOTE
Note: information on .o files is not available
File ‘/home/biocbuild/bbs-3.8-bioc/R/library/NuPoP/libs/NuPoP.so’:
  Found ‘_gfortran_st_close’, possibly from ‘close’ (Fortran)
  Found ‘_gfortran_st_open’, possibly from ‘open’ (Fortran)
  Found ‘_gfortran_st_read’, possibly from ‘read’ (Fortran)
  Found ‘_gfortran_st_write’, possibly from ‘write’ (Fortran), ‘print’
    (Fortran)

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs. The detected symbols are linked into the code but
might come from libraries and not actually be called.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
* checking files in ‘vignettes’ ... OK
* checking examples ... OK
Examples with CPU or elapsed time > 5s
               user system elapsed
NuPoP-package 6.480  0.020   6.529
predNuPoP     6.292  0.016   6.318
readNuPoP     5.660  0.012   5.676
* 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
* DONE

Status: 3 NOTEs
See
  ‘/home/biocbuild/bbs-3.8-bioc/meat/NuPoP.Rcheck/00check.log’
for details.

##############################################################################
##############################################################################
###
### Running command:
###
###   /home/biocbuild/bbs-3.8-bioc/R/bin/R CMD INSTALL NuPoP
###
##############################################################################
##############################################################################


* installing to library ‘/home/biocbuild/bbs-3.8-bioc/R/library’
* installing *source* package ‘NuPoP’ ...
** libs
gfortran  -fpic -g -O2  -c  vtbfb.f90 -o vtbfb.o
gfortran  -fpic -g -O2  -c  vtbfbNL4.f90 -o vtbfbNL4.o
gfortran -shared -L/home/biocbuild/bbs-3.8-bioc/R/lib -L/usr/local/lib -o NuPoP.so vtbfb.o vtbfbNL4.o -L/home/biocbuild/bbs-3.8-bioc/R/lib -lR
installing to /home/biocbuild/bbs-3.8-bioc/R/library/NuPoP/libs
** R
** inst
** byte-compile and prepare package for lazy loading
** help
*** installing help indices
** building package indices
** installing vignettes
** testing if installed package can be loaded
* DONE (NuPoP)

CHECK report for NuPoP on malbec1

Summary

Command output

Installation output

Tests output

Example timings

name	user	system	elapsed
NuPoP-package	6.480	0.020	6.529
plotNuPoP	0.088	0.000	0.088
predNuPoP	6.292	0.016	6.318
readNuPoP	5.660	0.012	5.676