===============================
R CMD BUILD
===============================
* checking for file ‘ReUseData/DESCRIPTION’ ... OK
* preparing ‘ReUseData’:
* checking DESCRIPTION meta-information ... OK
* installing the package to build vignettes
* creating vignettes ... OK
* checking for LF line-endings in source and make files and shell scripts
* checking for empty or unneeded directories
* building ‘ReUseData_0.99.28.tar.gz’
===============================
BiocCheckGitClone('ReUseData')
===============================
─ BiocCheckVersion: 1.35.9
─ BiocVersion: 3.17
─ Package: ReUseData
─ PackageVersion: 0.99.28
─ sourceDir: /home/pkgbuild/packagebuilder/workers/jobs/2868/d2d92a3c95be749fd402554d6b583a0dbdbcd12e/ReUseData
─ platform: unix
─ isTarBall: FALSE
* Checking valid files...
* Checking for stray BiocCheck output folders...
* Checking for inst/doc folders...
* Checking DESCRIPTION...
* Checking if DESCRIPTION is well formatted...
* Checking for valid maintainer...
* Checking CITATION...
─ BiocCheck results ──
0 ERRORS | 0 WARNINGS | 0 NOTES
For more details, run
browseVignettes(package = 'BiocCheck')
===============================
R CMD CHECK
===============================
* using log directory ‘/home/pkgbuild/packagebuilder/workers/jobs/2868/d2d92a3c95be749fd402554d6b583a0dbdbcd12e/ReUseData.Rcheck’
* using R Under development (unstable) (2023-01-10 r83596)
* using platform: x86_64-pc-linux-gnu (64-bit)
* R was compiled by
gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
GNU Fortran (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
* running under: Ubuntu 22.04.1 LTS
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘ReUseData/DESCRIPTION’ ... OK
* this is package ‘ReUseData’ version ‘0.99.28’
* package encoding: UTF-8
* 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 serialization versions ... OK
* checking whether package ‘ReUseData’ can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking for future file timestamps ... 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 ... [4s/4s] OK
* checking whether the package can be loaded with stated dependencies ... [4s/4s] OK
* checking whether the package can be unloaded cleanly ... [4s/4s] OK
* checking whether the namespace can be loaded with stated dependencies ... [4s/4s] OK
* checking whether the namespace can be unloaded cleanly ... [4s/4s] OK
* checking loading without being on the library search path ... [4s/4s] 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 ... [14s/14s] OK
* checking Rd files ... [0s/0s] OK
* checking Rd metadata ... OK
* checking Rd line widths ... 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 files in ‘vignettes’ ... OK
* checking examples ... [46s/47s] OK
Examples with CPU (user + system) or elapsed time > 5s
user system elapsed
dataUpdate 10.619 0.687 11.306
getCloudData 8.403 0.497 10.053
dataHub-class 6.315 0.431 6.747
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ...
Running ‘testthat.R’ [24s/25s]
[24s/25s] OK
* 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 ... [3s/3s] OK
* DONE
Status: OK
===============================
BiocCheck('ReUseData_0.99.28.tar.gz')
===============================
─ BiocCheckVersion: 1.35.9
─ BiocVersion: 3.17
─ Package: ReUseData
─ PackageVersion: 0.99.28
─ sourceDir: /tmp/RtmpkX2S1n/file683462a46ee38/ReUseData
─ installDir: /tmp/RtmpkX2S1n/file6834632d9434d
─ BiocCheckDir: /home/pkgbuild/packagebuilder/workers/jobs/2868/d2d92a3c95be749fd402554d6b583a0dbdbcd12e/ReUseData.BiocCheck
─ platform: unix
─ isTarBall: TRUE
* Installing package...
* Checking for deprecated package usage...
* Checking for remote package usage...
* Checking for 'LazyData: true' usage...
* Checking version number...
* Checking for version number mismatch...
* Checking new package version number...
* Checking R version dependency...
* Checking package size...
* Checking individual file sizes...
* Checking biocViews...
* Checking that biocViews are present...
* Checking package type based on biocViews...
Software
* Checking for non-trivial biocViews...
* Checking that biocViews come from the same category...
* Checking biocViews validity...
* Checking for recommended biocViews...
* NOTE: Consider adding these automatically suggested biocViews:
WorkflowManagement
Search 'biocViews' at https://contributions.bioconductor.org
* Checking build system compatibility...
* Checking for blank lines in DESCRIPTION...
* Checking if DESCRIPTION is well formatted...
* Checking for proper Description: field...
* Checking for whitespace in DESCRIPTION field names...
* Checking that Package field matches directory/tarball name...
* Checking for Version field...
* Checking for valid maintainer...
* Checking License: for restrictive use...
* Checking for pinned package versions...
* Checking DESCRIPTION/NAMESPACE consistency...
* Checking .Rbuildignore...
* Checking for stray BiocCheck output folders...
* Checking vignette directory...
* Checking whether vignette is built with 'R CMD build'...
* Checking package installation calls in R code...
* Checking for library/require of ReUseData...
* Checking coding practice...
* NOTE: Avoid using '=' for assignment and use '<-' instead
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
* NOTE: The recommended function length is 50 lines or less. There
are 41 functions greater than 50 lines.
* Checking man page documentation...
* NOTE: Consider adding runnable examples to man pages that
document exported objects.
* NOTE: Usage of dontrun{} / donttest{} tags found in man page
examples. 25% of man pages use at least one of these tags.
* NOTE: Use donttest{} instead of dontrun{}.
* Checking package NEWS...
* Checking unit tests...
* Checking skip_on_bioc() in tests...
* Checking formatting of DESCRIPTION, NAMESPACE, man pages, R source,
and vignette source...
* NOTE: Consider shorter lines; 35 lines (1%) are > 80 characters
long.
* NOTE: Consider 4 spaces instead of tabs; 2 lines (0%) contain
tabs.
* NOTE: Consider multiples of 4 spaces for line indents; 145 lines
(5%) are not.
See https://contributions.bioconductor.org/r-code.html
See styler package: https://cran.r-project.org/package=styler as
described in the BiocCheck vignette.
* Checking if package already exists in CRAN...
* Checking if new package already exists in Bioconductor...
* Checking for bioc-devel mailing list subscription...
Maintainer is subscribed to bioc-devel.
* Checking for support site registration...
Maintainer is registered at support site.
Package name is in support site watched tags.
─ BiocCheck results ──
0 ERRORS | 0 WARNINGS | 9 NOTES
See the ReUseData.BiocCheck folder and run
browseVignettes(package = 'BiocCheck')
for details.
===============================
R CMD BUILD
===============================
* checking for file ‘ReUseData/DESCRIPTION’ ... OK
* preparing ‘ReUseData’:
* checking DESCRIPTION meta-information ... OK
* installing the package to build vignettes
* creating vignettes ... ERROR
--- re-building ‘ReUseData_data.Rmd’ using rmarkdown
Quitting from lines 92-98 (ReUseData_data.Rmd)
Error: processing vignette 'ReUseData_data.Rmd' failed with diagnostics:
no method for coercing this S4 class to a vector
--- failed re-building ‘ReUseData_data.Rmd’
--- re-building ‘ReUseData_quickStart.Rmd’ using rmarkdown
Quitting from lines 76-85 (ReUseData_quickStart.Rmd)
Error: processing vignette 'ReUseData_quickStart.Rmd' failed with diagnostics:
no method for coercing this S4 class to a vector
--- failed re-building ‘ReUseData_quickStart.Rmd’
--- re-building ‘ReUseData_recipe.Rmd’ using rmarkdown
Quitting from lines 166-172 (ReUseData_recipe.Rmd)
Error: processing vignette 'ReUseData_recipe.Rmd' failed with diagnostics:
no method for coercing this S4 class to a vector
--- failed re-building ‘ReUseData_recipe.Rmd’
SUMMARY: processing the following files failed:
‘ReUseData_data.Rmd’ ‘ReUseData_quickStart.Rmd’
‘ReUseData_recipe.Rmd’
Error: Vignette re-building failed.
Execution halted