• using R version 4.5.2 (2025-10-31 ucrt)
• using platform: x86_64-w64-mingw32
• R was compiled by     gcc.exe (GCC) 14.3.0     GNU Fortran (GCC) 14.3.0
• running under: Windows Server 2022 x64 (build 20348)
• using session charset: UTF-8
• checking for file 'refseqR/DESCRIPTION' ... OK
• checking extension type ... Package
• this is package 'refseqR' version '1.1.5'
• 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 whether package 'refseqR' can be installed ... OK See the install log for details.
• checking installed package size ... OK
• checking package directory ... 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 ... [4s] OK
• checking whether the package can be loaded with stated dependencies ... [3s] OK
• checking whether the package can be unloaded cleanly ... [3s] OK
• checking whether the namespace can be loaded with stated dependencies ... [4s] OK
• checking whether the namespace can be unloaded cleanly ... [4s] OK
• checking loading without being on the library search path ... [4s] 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 ... [8s] OK
• checking Rd files ... [1s] OK
• checking Rd metadata ... 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 ... [8s] ERROR Running examples in 'refseqR-Ex.R' failed The error most likely occurred in: > ### Name: refseq_CDScoords > ### Title: Extract the coding sequences (CDS) coordinates from a transcript > ### accession > ### Aliases: refseq_CDScoords > > ### ** Examples > > transcript = c("XM_004487701") > refseq_CDScoords(transcript) Error in refseq_CDScoords(transcript) :   Exactly one CDS per file is expected. Contact the maintainer Execution halted
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes ... OK
• checking re-building of vignette outputs ... [9s] ERROR Error(s) in re-building vignettes: --- re-building 'refseqR.Rmd' using rmarkdown Quitting from refseqR.Rmd:109-111 [unnamed-chunk-10] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <error/rlang_error> Error in `refseq_CDScoords()`: ! Exactly one CDS per file is expected. Contact the maintainer --- Backtrace:     ▆  1. ├─base::substr(toString(refseq_CDSseq(transcript)), 1, 60)  2. ├─base::toString(refseq_CDSseq(transcript))  3. └─refseqR::refseq_CDSseq(transcript)  4. └─refseqR::refseq_CDScoords(transcript) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Error: processing vignette 'refseqR.Rmd' failed with diagnostics: Exactly one CDS per file is expected. Contact the maintainer --- failed re-building 'refseqR.Rmd' SUMMARY: processing the following file failed:   'refseqR.Rmd' Error: Vignette re-building failed. Execution halted
• checking PDF version of manual ... [19s] OK
• checking HTML version of manual ... [2s] OK
• DONE

Status: 2 ERRORs