===============================
R CMD BUILD
===============================
* checking for file ‘spbtest3/DESCRIPTION’ ... OK
* preparing ‘spbtest3’:
* checking DESCRIPTION meta-information ... OK
* installing the package (it is needed 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 ‘spbtest3_0.99.133.tar.gz’
===============================
BiocCheckGitClone('spbtest3')
===============================
── Running Git clone checks on spbtest3 ────────────────────────────────────────
* Checking valid files...
* Checking for inst/doc folders...
* Checking DESCRIPTION readability...
* Checking for valid use of maintainer fields...
✖ ERROR: Use either 'Authors@R' or 'Author' and 'Maintainer' fields. Do not use
both.
===============================
R CMD CHECK
===============================
* using log directory ‘/home/pkgbuild/packagebuilder/workers/jobs/51/spbtest3_20261120124445/spbtest3.Rcheck’
* using R version 4.6.1 (2026-06-24)
* using platform: x86_64-pc-linux-gnu
* R was compiled by
gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0
GNU Fortran (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0
* running under: Ubuntu 24.04.5 LTS
* using session charset: UTF-8
* current time: 2026-11-20 17:45:34 UTC
* using option ‘--no-vignettes’
* checking for file ‘spbtest3/DESCRIPTION’ ... OK
* this is package ‘spbtest3’ version ‘0.99.133’
* 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:
.github
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 serialization versions ... OK
* checking whether package ‘spbtest3’ 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 code files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... [0s/0s] OK
* checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
* checking whether the package can be unloaded cleanly ... [0s/0s] OK
* checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK
* checking whether the namespace can be unloaded cleanly ... [0s/0s] OK
* checking loading without being on the library search path ... [0s/0s] 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 ... [2s/2s] OK
* checking Rd files ... [0s/0s] OK
* checking Rd metadata ... NOTE
Rd files without \alias:
‘utils2.Rd’
* 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 ... WARNING
Undocumented arguments in Rd file 'test.Rd'
‘x’
Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking sizes of PDF files under ‘inst/doc’ ... INFO
‘qpdf’ is needed for checks on size reduction of PDFs
* checking files in ‘vignettes’ ... OK
* checking examples ... [0s/1s] OK
* checking for unstated dependencies in ‘tests’ ... OK
* checking tests ...
Running ‘testthat.R’ [1s/11s]
[1s/11s] ERROR
Running the tests in ‘tests/testthat.R’ failed.
Complete output:
> library(testthat)
> library(spbtest3)
>
> test_check("spbtest3")
Saving _problems/test-utils-4.R
[ FAIL 1 | WARN 0 | SKIP 0 | PASS 1 ]
══ Failed tests ════════════════════════════════════════════════════════════════
── Failure ('test-utils.R:4:5'): sbptest3 ──────────────────────────────────────
Expected `res` to equal FALSE.
Differences:
1 element mismatch
[ FAIL 1 | WARN 0 | SKIP 0 | PASS 1 ]
Error:
! Test failures.
Execution halted
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes ... 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: 1 ERROR, 1 WARNING, 2 NOTEs
See
‘/home/pkgbuild/packagebuilder/workers/jobs/51/spbtest3_20261120124445/spbtest3.Rcheck/00check.log’
for details.
===============================
BiocCheck('spbtest3_0.99.133.tar.gz')
===============================
── Installing spbtest3 ─────────────────────────────────────────────────────────
✔ Package installed successfully
── spbtest3 session metadata ───────────────────────────────────────────────────
→ sourceDir: /tmp/Rtmp39eQBU/file28815b1a4978a2/spbtest3
→ BiocVersion: 3.24
→ Package: spbtest3
→ PackageVersion: 0.99.133
→ BiocCheckDir: /home/pkgbuild/packagebuilder/workers/jobs/51/spbtest3_20261120124445/spbtest3.BiocCheck
→ BiocCheckVersion: 1.49.45
→ sourceDir: /tmp/Rtmp39eQBU/file28815b1a4978a2/spbtest3
→ installDir: /tmp/Rtmp39eQBU/file28815b11165288/lib
→ isTarBall: TRUE
→ platform: unix
── Running BiocCheck on spbtest3 ───────────────────────────────────────────────
* Checking for deprecated package usage...
adding rname 'https://bioconductor.org/checkResults/3.24/bioc-LATEST/meat-index.dcf'
* 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 if 'Package:' field matches directory / tarball...
* Checking for Version: field...
i NOTE: Consider adding the maintainer's ORCID iD in 'Authors@R' with
'comment=c(ORCID="...")'
* Checking DESCRIPTION readability...
* Checking validity of DESCRIPTION fields...
! WARNING: Unknown or non-standard DESCRIPTION field(s):
• 'DevelopmentURL'
* Checking License: for restrictive use...
* Checking for recommended DESCRIPTION fields...
i NOTE: Provide 'BugReports' field(s) in DESCRIPTION
* Checking for whitespace in DESCRIPTION field names...
* Checking for proper Description: field...
! WARNING: Description field in the DESCRIPTION file is too concise
* Checking for Bioconductor software dependencies...
! WARNING: No hard Bioconductor dependencies detected. Note that some
infrastructure packages may not have Bioconductor dependencies. For more
information, reach out to the Bioconductor community and/or consider a CRAN
submission.
* Checking for pinned package versions in DESCRIPTION...
* Checking for 'fnd' role in Authors@R...
i No 'fnd' role found in 'Authors@R'. If the work is supported by a grant,
consider adding the 'fnd' role to the list of authors.
* Checking for valid BiocType field...
✖ ERROR: Invalid 'BiocType' field in DESCRIPTION: 'Random'. Use one of:
Software, ExperimentData, Annotation, Workflow, Book, Docker. See
https://contributions.bioconductor.org/description.html#description-bioctype
* Checking CITATION...
i (Optional) CITATION file not found. Only include a CITATION file if there is
a preprint or publication for this Bioconductor package. Note that Bioconductor
packages are not required to have a CITATION file but it is useful both for
users and for tracking Bioconductor project-wide metrics. When including a
CITATION file, add the publication using the 'doi' argument of 'bibentry()'.
* Checking NAMESPACE...
* Checking .Rbuildignore...
* Checking for stray BiocCheck output folders...
* Checking vignette directory...
! WARNING: Use RMarkdown instead of Sweave 'Rnw' vignettes.
Rnw vignette(s) found:
• spbtest3.Rnw
• test.Rnw
i NOTE: Vignette(s) found with missing chunk labels
Found in files:
• spbtest3.Rnw
• ...
• test3.Rmd
! WARNING: Avoid class membership checks with class() / is() and == / !=; Use
is(x, 'class') for S4 classes
Found in files:
• test3.Rmd (code line 8, column 18)
! WARNING: Avoid T/F variables; If logical, use TRUE/FALSE
Found in files:
• vignettes/test.Rnw (chunk no. 1, line 8, column 13)
i NOTE: 'sessionInfo' not found in vignette(s)
Missing from file(s):
• vignettes/spbtest3.Rnw
• ...
• vignettes/test3.Rmd
* Checking whether vignette is built with 'R CMD build'...
* Checking package installation calls in R code...
* Checking for library/require of spbtest3...
* Checking coding practice...
i NOTE: Avoid 'cat' and 'print' outside of 'show' methods
Found in files:
• cat() in R/new_test.R (line 2, column 9)
• cat() in R/test.R (line 3, column 5)
• print() in R/utils.R (line 5, column 5)
i NOTE: Avoid using '=' for assignment and use '<-' instead
Found in files:
• R/utils.R (line 9, column 8)
! WARNING: Avoid T/F variables; If logical, use TRUE/FALSE
Found 5 times:
• T in R/test.R (line 21, column 10)
• ...
• T in R/utils.R (line 2, column 16)
! WARNING: Avoid class membership checks with class() / is() and == / !=; Use
is(x, 'class') for S4 classes
Found in files:
• R/utils.R (line 10, column 14)
! WARNING: Remove set.seed usage (found 1 times)
• set.seed() in R/test.R (line 38, column 5)
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
* Checking man page documentation...
i NOTE: Usage of dontrun / donttest tags found in man page examples. 67% of man
pages use at least one of these tags.
Found in files:
• test.Rd
• utils.Rd
i NOTE: Use donttest instead of dontrun.
Found in files:
• utils.Rd
* Checking package NEWS...
i 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...
i NOTE: Consider 4 spaces instead of tabs; 2 lines (1%) contain tabs.
First few lines:
• R/new_test.R#L2 cat("This is x",x) ...
• R/new_test.R#L3 x + 2 ...
i See https://contributions.bioconductor.org/r-code.html
i 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...
i Maintainer is subscribed to bioc-devel.
── BiocCheck v1.49.45 results ──────────────────────────────────────────────────
✖ 1 ERRORS | ⚠ 9 WARNINGS | i 10 NOTES
i See the spbtest3.BiocCheck folder and run
`browseVignettes(package = 'BiocCheck')`
for details.