* using log directory ‘/data/gannet/ripley/R/packages/tests-ATLAS/refseqR.Rcheck’ * using R Under development (unstable) (2024-04-16 r86435) * using platform: x86_64-pc-linux-gnu * R was compiled by gcc-13 (GCC) 13.2.0 GNU Fortran (GCC) 13.2.0 * running under: Fedora Linux 36 (Workstation Edition) * using session charset: UTF-8 * using option ‘--no-stop-on-test-error’ * checking for file ‘refseqR/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘refseqR’ version ‘1.0.1’ * 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 executable files ... OK * checking for hidden files and directories ... OK * checking for portable file names ... OK * checking for sufficient/correct file permissions ... OK * checking whether package ‘refseqR’ can be installed ... [23s/28s] 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 ... 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 ... [28s/38s] OK * checking Rd files ... 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 ... [8s/16s] ERROR Running examples in ‘refseqR-Ex.R’ failed The error most likely occurred in: > ### Name: refseq_description > ### Title: Get the sequence Description > ### Aliases: refseq_description > > ### ** Examples > > # Get the sequence descriptions from a set of XM accessions > xm = c("XM_004487701") > sapply(xm, function(x) refseq_description(x), USE.NAMES = FALSE) Error: HTTP failure: 500 NCBI/eutils202 - WWW Error 500 Diagnostic

Server Error

Your request could not be processed due to a problem on our Web server. This could be a transient problem, please try the query again. If it doesn't clear up within a reasonable period of time, e-mail a short description of your query and the diagnostic information shown below to:

pubmed@nlm.nih.gov - for problems with PubMed
webadmin@ncbi.nlm.nih.gov - for problems with other services

Thank you for your assistance. We will try to fix the problem as soon as possible.


Diagnostic Information:

Error: 500
URL: h t t p : / / e x t - h t t p - e u t i l s . l Execution halted * checking for unstated dependencies in vignettes ... OK * checking package vignettes ... OK * checking re-building of vignette outputs ... [24s/57s] OK * checking PDF version of manual ... [7s/12s] OK * checking HTML version of manual ... OK * checking for non-standard things in the check directory ... OK * checking for detritus in the temp directory ... OK * DONE Status: 1 ERROR See ‘/data/gannet/ripley/R/packages/tests-ATLAS/refseqR.Rcheck/00check.log’ for details. Command exited with non-zero status 1 Time 5:16.66, 193.33 + 21.50