chunknet - ChunkNet - check results
RForge.net

chunknet

About chunknet
GIT access
Download/Files
Check results
Package R docs

Version: 1.1
Result: WARNING
Check time: 2024-06-09 03:22
* using log directory ‘’
* using R Under development (unstable) (2023-11-28 r85645)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
gcc (Debian 10.2.1-6) 10.2.1 20210110
GNU Fortran (Debian 10.2.1-6) 10.2.1 20210110
* running under: Debian GNU/Linux 11 (bullseye)
* using session charset: UTF-8
* using option ‘--as-cran’
* checking for file ‘chunknet/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘chunknet’ version ‘1.1’
* 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 ‘chunknet’ can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking DESCRIPTION meta-information ... NOTE
Malformed Title field: should not end in a period.
License components which are templates and need '+ file LICENSE':
MIT
* 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 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
determine_locations: no visible global function definition for ‘relist’
disperse_arguments : : no visible global function definition
for ‘relist’
handle: no visible global function definition for ‘glob2rx’
Undefined global functions or variables:
glob2rx relist
Consider adding
importFrom("utils", "glob2rx", "relist")
to your NAMESPACE file.
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... WARNING
Undocumented code objects:
‘ChunkReferenceArray’ ‘LOCATOR’ ‘dapply’ ‘extract’
‘get_host_locations’ ‘is.ChunkReference’ ‘kill_all_nodes’
‘locator_node’ ‘post_locations’ ‘worker_node’
All user-level objects in a package should have documentation entries.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... WARNING
Objects in \usage without \alias in Rd file 'pull.Rd':
‘pull.ChunkReference’ ‘pull.character’ ‘pull.list’

Objects in \usage without \alias in Rd file 'push.Rd':
‘push.default’ ‘push.list’ ‘push.Chunk’

Objects in \usage without \alias in Rd file 'worker_node.Rd':
‘worker_node’ ‘locator_node’

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
S3 methods shown with full name in Rd file 'pull.Rd':
‘pull.ChunkReference’ ‘pull.character’ ‘pull.list’

S3 methods shown with full name in Rd file 'push.Rd':
‘push.default’ ‘push.list’ ‘push.Chunk’

The \usage entries for S3 methods should use the \method markup and not
their full name.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking examples ... OK
* checking PDF version of manual ... OK
* checking HTML version of manual ... OK
* checking for non-standard things in the check directory ... OK
* checking for detritus in the temp directory ... OK
* DONE

Status: 2 WARNINGs, 2 NOTEs
See
‘/00check.log’
for details.



Installation log: 00install.out

Distribution log

SVN checkout/GIT clone log