Bioconductor Single Package Builder - Build History

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

Hostname OS /Arch BUILD CHECK BUILD BIN POST-PROCESSING
merida1 macOS 10.14.6 Mojave/x86_64   OK     OK     OK     OK  
nebbiolo1 Linux (Ubuntu 20.04.4 LTS)/x86_64   OK     OK     skipped     OK  

merida1 Summary

[top]

Package: masstools
Version: 0.99.2
RVersion: 4.2
BiocVersion: 3.15
BuildCommand: /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R CMD build --keep-empty-dirs --no-resave-data masstools
BuildTime: 0 minutes 41.03 seconds
CheckCommand: BiocCheckGitClone('masstools') && /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R CMD check --no-vignettes --timings --no-multiarch masstools_0.99.2.tar.gz && BiocCheck('masstools_0.99.2.tar.gz', `new-package`=TRUE)
CheckTime: 1 minutes 49.26 seconds
BuildBinCommand: /Users/biocbuild/BBS/utils/build-universal.sh masstools_0.99.2.tar.gz /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R libdir
BuildBinTime: 0 minutes 13.89 seconds
PackageFileSize: 4515.56 KiB
BuildID:: masstools_20220113215825
PreProcessing: Starting Git clone. Installing dependencies. Checking Git Clone. Installing package: masstools. Starting Build package. Starting Check package. Starting Build 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. Build Package status: 0.

merida1 BUILD SRC output

[top]

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

 R CMD BUILD

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

* checking for file ‘masstools/DESCRIPTION’ ... OK
* preparing ‘masstools’:
* 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
Omitted ‘LazyData’ from DESCRIPTION
* building ‘masstools_0.99.2.tar.gz’


merida1 CHECK output

[top]

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

 BiocCheckGitClone('masstools')

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

This is BiocCheckGitClone version 1.31.24. 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.15/bioc/vignettes/BiocCheck/inst/doc/BiocCheck.html#interpreting-bioccheck-output




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

 R CMD CHECK

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

* using log directory ‘/Users/pkgbuild/packagebuilder/workers/jobs/2481/011495db5f909ebdc10ae3c739d861a3860be370/masstools.Rcheck’
* using R Under development (unstable) (2022-01-05 r81451)
* using platform: x86_64-apple-darwin17.0 (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘masstools/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘masstools’ version ‘0.99.2’
* 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 whether package ‘masstools’ can be installed ... [11s/12s] OK
* checking installed package size ... NOTE
  installed size is  9.6Mb
  sub-directories of 1Mb or more:
    doc         6.3Mb
    rmarkdown   2.3Mb
* 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 ... [14s/14s] OK
* checking Rd files ... [1s/1s] 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 installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [7s/13s] OK
Examples with CPU (user + system) or elapsed time > 5s
                    user system elapsed
get_compound_class 0.206  0.017   5.388
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ...
  Running ‘testthat.R’ [3s/3s]
 [3s/3s] 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: 1 NOTE
See
  ‘/Users/pkgbuild/packagebuilder/workers/jobs/2481/011495db5f909ebdc10ae3c739d861a3860be370/masstools.Rcheck/00check.log’
for details.






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

 BiocCheck('masstools_0.99.2.tar.gz')

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

This is BiocCheck version 1.31.24. 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 for pinned package versions...
* Checking DESCRIPTION/NAMESPACE consistency...
* Checking .Rbuildignore...
* Checking vignette directory...
    * NOTE: 'sessionInfo' not found in vignette(s)
      Missing from file(s):
        vignettes/contact_us.Rmd
* Checking whether vignette is built with 'R CMD build'...
* Checking package installation calls in R code...
* Checking for library/require of masstools...
* Checking coding practice...
    * NOTE: Avoid 'cat' and 'print' outside of 'show' methods
      Found in files:
        cat() in R/masstools_logo.R (line 36, column 3)
    * NOTE: Avoid the use of 'paste' in condition signals
      Found in files:
        R/classyfire.R (line 236, column 23)
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
    * NOTE: Recommended function length <= 50 lines.
      There are 12 functions > 50 lines.
      The longest 5 functions are:
        ms2_plot() (R/ms2_plot.R, line 57): 213 lines
        get_compound_class() (R/classyfire.R, line 16): 201 lines
        trans_ID() (R/trans_ID.R, line 30): 164 lines
        trans_id_database() (R/trans_ID.R, line 207): 134 lines
        split_formula() (R/adduct_formula.R, line 118): 113 lines
* Checking man page documentation...
    * NOTE: Consider adding runnable examples to the following man
      pages which document exported objects:
      read_mgf.Rd, setwd_project.Rd, setwd_win.Rd
* Checking package NEWS...
    * NOTE: Consider adding a NEWS file, so your package news will be
      included in Bioconductor release announcements.
* 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; 23 lines (1%) are > 80 characters
      long.
    First 6 lines:
      R/classyfire.R:257             message("Mass: ", dplyr::pull(object@com...
      R/masstools_logo.R:54 # # writeLines(capture.output(say("Hello"), type ...
      R/masstools_logo.R:59 #     "| '_ ` _ \\ / _ \\ __|  / /\\/ /\\ /", "| ...
      R/trans_ID.R:94                     dplyr::filter(!name %in% c("[", "]"...
      R/trans_ID.R:220             xml2::read_html("http://cts.fiehnlab.ucdav...
      R/trans_ID.R:222             xml2::read_html("http://cts.fiehnlab.ucdav...
    * NOTE: Consider multiples of 4 spaces for line indents, 299
      lines(9%) are not.
    First 6 lines:
      R/adduct_formula.R:17              adduct = "M-H2O+H") {
      R/adduct_formula.R:72                           collapse = "")
      R/adduct_formula.R:85                            sum(x$number),
      R/adduct_formula.R:86                            stringsAsFactors = FALSE)
      R/adduct_formula.R:98                           collapse = "")
      R/adduct_formula.R:166                                          double....
    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: 8
For detailed information about these checks, see the BiocCheck
vignette, available at
https://bioconductor.org/packages/3.15/bioc/vignettes/BiocCheck/inst/doc/BiocCheck.html#interpreting-bioccheck-output

merida1 BUILD BIN output

[top]

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

 R CMD BUILD

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

>>>>>>> 
>>>>>>> INSTALLATION WITH 'R CMD INSTALL --preclean --no-multiarch --library=libdir masstools_0.99.2.tar.gz'
>>>>>>> 

* installing *source* package ‘masstools’ ...
** using staged installation
** R
** inst
** byte-compile and prepare package for lazy loading
Note: wrong number of arguments to '==' 
** help
*** installing help indices
*** copying figures
** building package indices
** installing vignettes
** testing if installed package can be loaded from temporary location
** testing if installed package can be loaded from final location
** testing if installed package keeps a record of temporary installation path
* DONE (masstools)



nebbiolo1 Summary

[top]

Package: masstools
Version: 0.99.2
RVersion: 4.2
BiocVersion: 3.15
BuildCommand: /home/biocbuild/bbs-3.15-bioc/R/bin/R CMD build --keep-empty-dirs --no-resave-data masstools
BuildTime: 0 minutes 22.70 seconds
CheckCommand: BiocCheckGitClone('masstools') && /home/biocbuild/bbs-3.15-bioc/R/bin/R CMD check --no-vignettes --timings masstools_0.99.2.tar.gz && BiocCheck('masstools_0.99.2.tar.gz', `new-package`=TRUE)
CheckTime: 0 minutes 59.52 seconds
BuildBinCommand:
BuildBinTime:
PackageFileSize: 4515.32 KiB
BuildID:: masstools_20220113215825
PreProcessing: Starting Git clone. Installing dependencies. Checking Git Clone. Installing package: masstools. 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 ‘masstools/DESCRIPTION’ ... OK
* preparing ‘masstools’:
* 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
Omitted ‘LazyData’ from DESCRIPTION
* building ‘masstools_0.99.2.tar.gz’


nebbiolo1 CHECK output

[top]

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

 BiocCheckGitClone('masstools')

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

This is BiocCheckGitClone version 1.31.24. 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.15/bioc/vignettes/BiocCheck/inst/doc/BiocCheck.html#interpreting-bioccheck-output




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

 R CMD CHECK

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

* using log directory ‘/home/pkgbuild/packagebuilder/workers/jobs/2481/011495db5f909ebdc10ae3c739d861a3860be370/masstools.Rcheck’
* using R Under development (unstable) (2022-01-05 r81451)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘masstools/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘masstools’ version ‘0.99.2’
* 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 whether package ‘masstools’ can be installed ... [6s/6s] OK
* checking installed package size ... NOTE
  installed size is  6.5Mb
  sub-directories of 1Mb or more:
    doc         3.6Mb
    rmarkdown   1.9Mb
* 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 ... [7s/7s] 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 installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [5s/11s] OK
Examples with CPU (user + system) or elapsed time > 5s
                    user system elapsed
get_compound_class 0.189   0.02   5.332
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ...
  Running ‘testthat.R’ [1s/1s]
 [2s/2s] 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: 1 NOTE
See
  ‘/home/pkgbuild/packagebuilder/workers/jobs/2481/011495db5f909ebdc10ae3c739d861a3860be370/masstools.Rcheck/00check.log’
for details.






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

 BiocCheck('masstools_0.99.2.tar.gz')

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

This is BiocCheck version 1.31.24. 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 for pinned package versions...
* Checking DESCRIPTION/NAMESPACE consistency...
* Checking .Rbuildignore...
* Checking vignette directory...
    * NOTE: 'sessionInfo' not found in vignette(s)
      Missing from file(s):
        vignettes/contact_us.Rmd
* Checking whether vignette is built with 'R CMD build'...
* Checking package installation calls in R code...
* Checking for library/require of masstools...
* Checking coding practice...
    * NOTE: Avoid 'cat' and 'print' outside of 'show' methods
      Found in files:
        cat() in R/masstools_logo.R (line 36, column 3)
    * NOTE: Avoid the use of 'paste' in condition signals
      Found in files:
        R/classyfire.R (line 236, column 23)
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
    * NOTE: Recommended function length <= 50 lines.
      There are 12 functions > 50 lines.
      The longest 5 functions are:
        ms2_plot() (R/ms2_plot.R, line 57): 213 lines
        get_compound_class() (R/classyfire.R, line 16): 201 lines
        trans_ID() (R/trans_ID.R, line 30): 164 lines
        trans_id_database() (R/trans_ID.R, line 207): 134 lines
        split_formula() (R/adduct_formula.R, line 118): 113 lines
* Checking man page documentation...
    * NOTE: Consider adding runnable examples to the following man
      pages which document exported objects:
      read_mgf.Rd, setwd_project.Rd, setwd_win.Rd
* Checking package NEWS...
    * NOTE: Consider adding a NEWS file, so your package news will be
      included in Bioconductor release announcements.
* 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; 23 lines (1%) are > 80 characters
      long.
    First 6 lines:
      R/classyfire.R:257             message("Mass: ", dplyr::pull(object@com...
      R/masstools_logo.R:54 # # writeLines(capture.output(say("Hello"), type ...
      R/masstools_logo.R:59 #     "| '_ ` _ \\ / _ \\ __|  / /\\/ /\\ /", "| ...
      R/trans_ID.R:94                     dplyr::filter(!name %in% c("[", "]"...
      R/trans_ID.R:220             xml2::read_html("http://cts.fiehnlab.ucdav...
      R/trans_ID.R:222             xml2::read_html("http://cts.fiehnlab.ucdav...
    * NOTE: Consider multiples of 4 spaces for line indents, 299
      lines(9%) are not.
    First 6 lines:
      R/adduct_formula.R:17              adduct = "M-H2O+H") {
      R/adduct_formula.R:72                           collapse = "")
      R/adduct_formula.R:85                            sum(x$number),
      R/adduct_formula.R:86                            stringsAsFactors = FALSE)
      R/adduct_formula.R:98                           collapse = "")
      R/adduct_formula.R:166                                          double....
    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: 8
For detailed information about these checks, see the BiocCheck
vignette, available at
https://bioconductor.org/packages/3.15/bioc/vignettes/BiocCheck/inst/doc/BiocCheck.html#interpreting-bioccheck-output

nebbiolo1 BUILD BIN output

[top]