Bioconductor Single Package Builder - Build History

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

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

nebbiolo2 Summary

[top]

Package: COTAN
Version: 0.99.8
RVersion: 4.1
BiocVersion: 3.14
BuildCommand: /home/biocbuild/bbs-3.14-bioc/R/bin/R CMD build --keep-empty-dirs --no-resave-data COTAN
BuildTime: 1 minutes 19.30 seconds
CheckCommand: BiocCheckGitClone('COTAN') && /home/biocbuild/bbs-3.14-bioc/R/bin/R CMD check --no-vignettes --timings COTAN_0.99.8.tar.gz && BiocCheck('COTAN_0.99.8.tar.gz', `new-package`=TRUE)
CheckTime: 2 minutes 9.71 seconds
BuildBinCommand:
BuildBinTime:
PackageFileSize: 3399.58 KiB
BuildID:: COTAN_20210718194842
PreProcessing: Starting Git clone. Installing dependencies. Checking Git Clone. Installing package: COTAN. 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.

nebbiolo2 BUILD SRC output

[top]

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

 R CMD BUILD

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

* checking for file ‘COTAN/DESCRIPTION’ ... OK
* preparing ‘COTAN’:
* 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
* looking to see if a ‘data/datalist’ file should be added
* building ‘COTAN_0.99.8.tar.gz’


nebbiolo2 CHECK output

[top]

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

 BiocCheckGitClone('COTAN')

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

This is BiocCheckGitClone version 1.29.9. BiocCheckGitClone is a work
in progress. Output and severity of issues may change.
* Checking valid files...
* Checking DESCRIPTION...
* Checking if DESCRIPTION is well formatted...
* Checking for valid maintainer...
* Checking CITATION...


Summary:
ERROR count: 0
WARNING count: 0
NOTE count: 0
For detailed information about these checks, see the BiocCheck
vignette, available at
https://bioconductor.org/packages/3.14/bioc/vignettes/BiocCheck/inst/doc/BiocCheck.html#interpreting-bioccheck-output




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

 R CMD CHECK

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

* using log directory ‘/home/pkgbuild/packagebuilder/workers/jobs/2151/3d050ffd6560283ec635f0a311294f26b502b04e/COTAN.Rcheck’
* using R version 4.1.0 beta (2021-05-03 r80259)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘COTAN/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘COTAN’ version ‘0.99.8’
* 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 ... NOTE
Found the following hidden files and directories:
  .BBSoptions
These were most likely included in error. See section ‘Package
structure’ in the ‘Writing R Extensions’ manual.
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking whether package ‘COTAN’ can be installed ... [11s/11s] 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 ... 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 ... [9s/9s] NOTE
automatic.COTAN.object.creation,data.frame: no visible binding for
  global variable ‘means’
automatic.COTAN.object.creation,data.frame: no visible binding for
  global variable ‘PC1’
automatic.COTAN.object.creation,data.frame: no visible binding for
  global variable ‘PC2’
automatic.COTAN.object.creation,data.frame: no visible binding for
  global variable ‘nu’
clean,scCOTAN: no visible binding for global variable ‘PC1’
clean,scCOTAN: no visible binding for global variable ‘PC2’
fun_linear,scCOTAN : <anonymous>: no visible global function definition
  for ‘python_PCA’
plot_GDI,scCOTAN: no visible binding for global variable ‘sum.raw.norm’
plot_heatmap,ANY: no visible binding for global variable ‘time’
plot_heatmap,ANY: no visible binding for global variable ‘g2’
Undefined global functions or variables:
  PC1 PC2 g2 means nu python_PCA sum.raw.norm time
Consider adding
  importFrom("stats", "time")
to your NAMESPACE file.
* 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 ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking R/sysdata.rda ... OK
* checking line endings in shell scripts ... OK
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [48s/30s] OK
Examples with CPU (user + system) or elapsed time > 5s
                                  user system elapsed
automatic.COTAN.object.creation 20.682 10.622  18.768
clean                            1.667  4.529   0.663
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ...
  Running ‘spelling.R’ [0s/0s]
  Comparing ‘spelling.Rout’ to ‘spelling.Rout.save’ ...6c6
< NULL
---
> All Done!
  Running ‘testthat.R’ [44s/25s]
 [45s/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 ... OK
* DONE

Status: 2 NOTEs
See
  ‘/home/pkgbuild/packagebuilder/workers/jobs/2151/3d050ffd6560283ec635f0a311294f26b502b04e/COTAN.Rcheck/00check.log’
for details.






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

 BiocCheck('COTAN_0.99.8.tar.gz')

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

This is BiocCheck version 1.29.9. BiocCheck is a work in progress.
Output and severity of issues may change. Installing package...
* Checking Package Dependencies...
* Checking if other packages can import this one...
* Checking to see if we understand object initialization...
* 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...
* Checking DESCRIPTION/NAMESPACE consistency...
* Checking .Rbuildignore...
* Checking vignette directory...
* Checking whether vignette is built with 'R CMD build'...
* Checking package installation calls in R code...
* Checking for library/require of COTAN...
* Checking coding practice...
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...............................
    * NOTE: Recommended function length <= 50 lines.
      There are 9 functions > 50 lines.
      The longest 5 functions are:
        _anonymous_.523() (R/COTAN_main.R, line 523): 152 lines
        _anonymous_.718() (R/COTAN_main.R, line 718): 135 lines
        _anonymous_.1140() (R/COTAN_main.R, line 1140): 134 lines
        _anonymous_.120() (R/COTAN_main.R, line 120): 123 lines
        _anonymous_.887() (R/COTAN_main.R, line 887): 73 lines
* Checking man page documentation...
    * NOTE: Consider adding runnable examples to the following man
      pages which document exported objects:
      plot_general.heatmap.Rd, plot_heatmap.Rd
    * NOTE: Usage of dontrun{} / donttest{} found in man page examples.
      7% of man pages use one of these cases.
      Found in the following files:
        plot_general.heatmap.Rd
        plot_heatmap.Rd
    * NOTE: Use donttest{} instead of dontrun{}.
      Found in the following files:
        plot_general.heatmap.Rd
        plot_heatmap.Rd
* 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; 328 lines (9%) are > 80 characters
      long.
    First 6 lines:
      R/COTAN_main.R:38 #' @param object the dataframe containing the raw dat...
      R/COTAN_main.R:125                                                     ...
      R/COTAN_main.R:128                                                     ...
      R/COTAN_main.R:129                                    axis.text.y = ele...
      R/COTAN_main.R:132                                                     ...
      R/COTAN_main.R:134                                                     ...
    * NOTE: Consider multiples of 4 spaces for line indents, 1098
      lines(31%) are not.
    First 6 lines:
      R/COTAN_main.R:62                    is.null(attr(object@raw, "class")) ){
      R/COTAN_main.R:64                                              "sparseM...
      R/COTAN_main.R:76               #object@clusters = rep(NA,ncol(object@r...
      R/COTAN_main.R:77               #names(object@clusters)=colnames(object...
      R/COTAN_main.R:79           }
      R/COTAN_main.R:120               function(object) {
    See http://bioconductor.org/developers/how-to/coding-style/
    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.


Summary:
ERROR count: 0
WARNING count: 0
NOTE count: 6
For detailed information about these checks, see the BiocCheck
vignette, available at
https://bioconductor.org/packages/3.14/bioc/vignettes/BiocCheck/inst/doc/BiocCheck.html#interpreting-bioccheck-output

nebbiolo2 BUILD BIN output

[top]