Bioconductor Single Package Builder - Build History

Snapshot Date: 
URL:  https://git.bioconductor.org/packages/cfTools
Last Changed Rev:  / Revision: 
Last Changed Date: 

Hostname OS /Arch BUILD CHECK BUILD BIN POST-PROCESSING
nebbiolo1 Linux (Ubuntu 22.04.1 LTS)/x86_64   OK     OK     skipped     OK  

nebbiolo1 Summary

[top]

Package: cfTools
Version: 0.99.3
RVersion: 4.3
BiocVersion: 3.17
BuildCommand: /home/biocbuild/bbs-3.17-bioc/R/bin/R CMD build --keep-empty-dirs --no-resave-data cfTools
BuildTime: 0 minutes 52.68 seconds
CheckCommand: BiocCheckGitClone('cfTools') && /home/biocbuild/bbs-3.17-bioc/R/bin/R CMD check --no-vignettes --timings --library=/home/pkgbuild/packagebuilder/workers/jobs/2963/R-libs --install=check:/home/pkgbuild/packagebuilder/workers/jobs/2963/f604bebb65b0455d91d9fc64ac564b31c00a6655/cfTools.install-out.txt cfTools_0.99.3.tar.gz && BiocCheck('cfTools_0.99.3.tar.gz', `new-package`=TRUE)
CheckTime: 1 minutes 54.65 seconds
BuildBinCommand:
BuildBinTime:
PackageFileSize: 458.62 KiB
BuildID:: cfTools_20230405070109
PreProcessing: Starting Git clone. Installing dependencies. Checking Git Clone. Installing package: cfTools. Starting Build package. Starting Check package.
PostProcessing: Finished Git clone. Package type: Software. Installing dependency status: 0. Checking git clone status: 0. Installing package status: 0. Build Package status: 0. Checking Package status: 0.

nebbiolo1 BUILD SRC output

[top]

===============================

 R CMD BUILD

===============================

* checking for file ‘cfTools/DESCRIPTION’ ... OK
* preparing ‘cfTools’:
* checking DESCRIPTION meta-information ... OK
* cleaning src
* installing the package to build vignettes
* creating vignettes ... OK
* cleaning src
* checking for LF line-endings in source and make files and shell scripts
* checking for empty or unneeded directories
* looking to see if a ‘data/datalist’ file should be added
* building ‘cfTools_0.99.3.tar.gz’


nebbiolo1 CHECK output

[top]

===============================

 BiocCheckGitClone('cfTools')

===============================

─ BiocCheckVersion: 1.35.17
─ BiocVersion: 3.17
─ Package: cfTools
─ PackageVersion: 0.99.3
─ sourceDir: /home/pkgbuild/packagebuilder/workers/jobs/2963/f604bebb65b0455d91d9fc64ac564b31c00a6655/cfTools
─ 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/2963/f604bebb65b0455d91d9fc64ac564b31c00a6655/cfTools.Rcheck’
* using R version 4.3.0 alpha (2023-04-03 r84154)
* 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.2 LTS
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘cfTools/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘cfTools’ version ‘0.99.3’
* 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 ‘cfTools’ can be installed ... NOTE
Found the following notes/warnings:
  Non-staged installation was used
See ‘/home/pkgbuild/packagebuilder/workers/jobs/2963/f604bebb65b0455d91d9fc64ac564b31c00a6655/cfTools.Rcheck/00install.out’ for details.
* used C++ compiler: ‘g++ (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0’
* 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 ... [2s/2s] OK
* checking whether the package can be loaded with stated dependencies ... [2s/2s] OK
* checking whether the package can be unloaded cleanly ... [3s/3s] OK
* checking whether the namespace can be loaded with stated dependencies ... [3s/3s] OK
* checking whether the namespace can be unloaded cleanly ... [3s/3s] OK
* checking loading without being on the library search path ... [3s/3s] 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 ... [10s/10s] 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 contents of ‘data’ directory ... OK
* checking data for non-ASCII characters ... [0s/0s] OK
* checking data for ASCII and uncompressed saves ... 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 ... NOTE
Note: information on .o files is not available
* checking files in ‘vignettes’ ... OK
* checking examples ... [96s/26s] OK
Examples with CPU (user + system) or elapsed time > 5s
                 user system elapsed
CancerDetector 15.269 76.534  21.315
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ...
  Running ‘testthat.R’ [92s/19s]
 [92s/20s] 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: 2 NOTEs
See
  ‘/home/pkgbuild/packagebuilder/workers/jobs/2963/f604bebb65b0455d91d9fc64ac564b31c00a6655/cfTools.Rcheck/00check.log’
for details.






===============================

 BiocCheck('cfTools_0.99.3.tar.gz')

===============================

─ BiocCheckVersion: 1.35.17
─ BiocVersion: 3.17
─ Package: cfTools
─ PackageVersion: 0.99.3
─ sourceDir: /tmp/RtmpjgXWl6/file107b2e791f6e86/cfTools
─ installDir: /tmp/RtmpjgXWl6/file107b2e4ce4dd07
─ BiocCheckDir: /home/pkgbuild/packagebuilder/workers/jobs/2963/f604bebb65b0455d91d9fc64ac564b31c00a6655/cfTools.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...
* 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...
    * NOTE: License 'file LICENSE' unknown; licenses cannot restrict
      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 cfTools...
* Checking coding practice...
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
* Checking man page documentation...
* 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; 10 lines (1%) are > 80 characters
      long.
    * NOTE: Consider multiples of 4 spaces for line indents; 34 lines
      (2%) 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 | 3 NOTES

See the cfTools.BiocCheck folder and run
    browseVignettes(package = 'BiocCheck')
for details.

nebbiolo1 BUILD BIN output

[top]