nebbiolo1 Summary
[top]
Package: proteasy |
Version: 0.99.3 |
RVersion: 4.2
|
BiocVersion: 3.15
|
BuildCommand: /home/biocbuild/bbs-3.15-bioc/R/bin/R CMD build --keep-empty-dirs --no-resave-data proteasy |
BuildTime: 0 minutes 24.67 seconds |
CheckCommand: BiocCheckGitClone('proteasy') && /home/biocbuild/bbs-3.15-bioc/R/bin/R CMD check --no-vignettes --timings proteasy_0.99.3.tar.gz && BiocCheck('proteasy_0.99.3.tar.gz', `new-package`=TRUE) |
CheckTime: 0 minutes 56.28 seconds |
BuildBinCommand: |
BuildBinTime: |
PackageFileSize: 3019.53 KiB |
BuildID:: proteasy_20220527170633 |
PreProcessing: Starting Git clone. Installing dependencies. Checking Git Clone. Installing package: proteasy. 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: 1. |
nebbiolo1 BUILD SRC output
[top]
===============================
R CMD BUILD
===============================
* checking for file ‘proteasy/DESCRIPTION’ ... OK
* preparing ‘proteasy’:
* checking DESCRIPTION meta-information ... OK
* installing the package to process help pages
* saving partial Rd database
* 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 ‘proteasy_0.99.3.tar.gz’
nebbiolo1 CHECK output
[top]
===============================
BiocCheckGitClone('proteasy')
===============================
─ BiocCheckVersion: 1.32.0
─ BiocVersion: 3.15
─ Package: proteasy
─ PackageVersion: 0.99.3
─ sourceDir: /home/pkgbuild/packagebuilder/workers/jobs/2660/proteasy_20220527170633/proteasy
─ platform: unix
─ isTarBall: FALSE
* Checking valid files...
* Checking for stray BiocCheck output 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/2660/proteasy_20220527170633/proteasy.Rcheck’
* using R version 4.2.0 (2022-04-22)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘proteasy/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘proteasy’ 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 whether package ‘proteasy’ can be installed ... [12s/12s] 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 ... [4s/4s] 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 R/sysdata.rda ... OK
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [50s/16s] OK
Examples with CPU (user + system) or elapsed time > 5s
user system elapsed
cleavages 15.807 0.870 10.600
searchProtease 12.592 0.010 0.457
searchSubstrate 6.217 0.005 0.193
* 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: OK
===============================
BiocCheck('proteasy_0.99.3.tar.gz')
===============================
─ BiocCheckVersion: 1.32.0
─ BiocVersion: 3.15
─ Package: proteasy
─ PackageVersion: 0.99.3
─ sourceDir: /tmp/RtmpMl517e/file2757f4378d28f5/proteasy
─ installDir: /tmp/RtmpMl517e/file2757f4252890d6
─ BiocCheckDir: /home/pkgbuild/packagebuilder/workers/jobs/2660/proteasy_20220527170633/proteasy.BiocCheck
─ platform: unix
─ isTarBall: TRUE
* 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...
* NOTE: The Description field in the DESCRIPTION is made up by less
than 3 sentences. Please consider expanding this field, and
structure it as a full paragraph
* 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 proteasy...
* Checking coding practice...
* NOTE: Avoid 1:...; use seq_len() or seq_along()
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
* NOTE: Recommended function length <= 50 lines.There are 1
functions > 50 lines.
* Checking man page documentation...
* NOTE: Consider adding runnable examples to man pages that
documentexported objects.
* NOTE: Usage of dontrun{} / donttest{} found in man page
examples.12% of man pages use one of these cases.
* NOTE: Use donttest{} instead of dontrun{}.
* Checking package NEWS...
* Checking unit tests...
* NOTE: Consider adding unit tests. We strongly encourage them. See
http://bioconductor.org/developers/how-to/unitTesting-guidelines/.
* Checking skip_on_bioc() in tests...
* Checking formatting of DESCRIPTION, NAMESPACE, man pages, R source,
and vignette source...
* NOTE: Consider shorter lines; 67 lines (8%) are > 80 characters
long.
* NOTE: Consider multiples of 4 spaces for line indents; 32 lines
(4%) are not.
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...
* ERROR: Maintainer must subscribe to the bioc-devel mailing list.
Subscribe here: https://stat.ethz.ch/mailman/listinfo/bioc-devel
* Checking for support site registration...
Maintainer is registered at support site.
Package name is in support site watched tags.
─ BiocCheck results ──
1 ERRORS | 0 WARNINGS | 9 NOTES
See the proteasy.BiocCheck folder and run
browseVignettes(package = 'BiocCheck')
for details.
nebbiolo1 BUILD BIN output
[top]
merida1 Summary
[top]
Package: proteasy |
Version: 0.99.3 |
RVersion: 4.2
|
BiocVersion: 3.15
|
BuildCommand: /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R CMD build --keep-empty-dirs --no-resave-data proteasy |
BuildTime: 0 minutes 35.00 seconds |
CheckCommand: BiocCheckGitClone('proteasy') && /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R CMD check --no-vignettes --timings --no-multiarch proteasy_0.99.3.tar.gz && BiocCheck('proteasy_0.99.3.tar.gz', `new-package`=TRUE) |
CheckTime: 1 minutes 17.57 seconds |
BuildBinCommand: /Users/biocbuild/BBS/utils/build-universal.sh proteasy_0.99.3.tar.gz /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R libdir |
BuildBinTime: 0 minutes 16.41 seconds |
PackageFileSize: 3019.20 KiB |
BuildID:: proteasy_20220527170633 |
PreProcessing: Starting Git clone. Installing dependencies. Checking Git Clone. Installing package: proteasy. 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: 1. Build Package status: 0. |
merida1 BUILD SRC output
[top]
===============================
R CMD BUILD
===============================
* checking for file ‘proteasy/DESCRIPTION’ ... OK
* preparing ‘proteasy’:
* checking DESCRIPTION meta-information ... OK
* installing the package to process help pages
* saving partial Rd database
* 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 ‘proteasy_0.99.3.tar.gz’
merida1 CHECK output
[top]
===============================
BiocCheckGitClone('proteasy')
===============================
─ BiocCheckVersion: 1.32.0
─ BiocVersion: 3.15
─ Package: proteasy
─ PackageVersion: 0.99.3
─ sourceDir: /Users/pkgbuild/packagebuilder/workers/jobs/2660/proteasy_20220527170633/proteasy
─ platform: unix
─ isTarBall: FALSE
* Checking valid files...
* Checking for stray BiocCheck output 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 ‘/Users/pkgbuild/packagebuilder/workers/jobs/2660/proteasy_20220527170633/proteasy.Rcheck’
* using R version 4.2.0 (2022-04-22)
* using platform: x86_64-apple-darwin17.0 (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘proteasy/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘proteasy’ 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 whether package ‘proteasy’ can be installed ... [16s/16s] 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 ... [5s/5s] 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 R/sysdata.rda ... OK
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [19s/19s] OK
Examples with CPU (user + system) or elapsed time > 5s
user system elapsed
cleavages 13.064 0.57 13.635
* 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: OK
===============================
BiocCheck('proteasy_0.99.3.tar.gz')
===============================
─ BiocCheckVersion: 1.32.0
─ BiocVersion: 3.15
─ Package: proteasy
─ PackageVersion: 0.99.3
─ sourceDir: /tmp/RtmpY9Cq5n/file1850045741b05/proteasy
─ installDir: /tmp/RtmpY9Cq5n/file185001fbd532e
─ BiocCheckDir: /Users/pkgbuild/packagebuilder/workers/jobs/2660/proteasy_20220527170633/proteasy.BiocCheck
─ platform: unix
─ isTarBall: TRUE
* 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...
* NOTE: The Description field in the DESCRIPTION is made up by less
than 3 sentences. Please consider expanding this field, and
structure it as a full paragraph
* 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 proteasy...
* Checking coding practice...
* NOTE: Avoid 1:...; use seq_len() or seq_along()
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
* NOTE: Recommended function length <= 50 lines.There are 1
functions > 50 lines.
* Checking man page documentation...
* NOTE: Consider adding runnable examples to man pages that
documentexported objects.
* NOTE: Usage of dontrun{} / donttest{} found in man page
examples.12% of man pages use one of these cases.
* NOTE: Use donttest{} instead of dontrun{}.
* Checking package NEWS...
* Checking unit tests...
* NOTE: Consider adding unit tests. We strongly encourage them. See
http://bioconductor.org/developers/how-to/unitTesting-guidelines/.
* Checking skip_on_bioc() in tests...
* Checking formatting of DESCRIPTION, NAMESPACE, man pages, R source,
and vignette source...
* NOTE: Consider shorter lines; 67 lines (8%) are > 80 characters
long.
* NOTE: Consider multiples of 4 spaces for line indents; 32 lines
(4%) are not.
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...
* ERROR: Maintainer must subscribe to the bioc-devel mailing list.
Subscribe here: https://stat.ethz.ch/mailman/listinfo/bioc-devel
* Checking for support site registration...
Maintainer is registered at support site.
Package name is in support site watched tags.
─ BiocCheck results ──
1 ERRORS | 0 WARNINGS | 9 NOTES
See the proteasy.BiocCheck folder and run
browseVignettes(package = 'BiocCheck')
for details.
merida1 BUILD BIN output
[top]
===============================
R CMD BUILD
===============================
>>>>>>>
>>>>>>> INSTALLATION WITH 'R CMD INSTALL --preclean --no-multiarch --library=libdir proteasy_0.99.3.tar.gz'
>>>>>>>
* installing *source* package ‘proteasy’ ...
** using staged installation
** R
** inst
** byte-compile and prepare package for lazy loading
** help
*** installing help indices
** 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 (proteasy)