Re: [R-pkg-devel] checking CRAN incoming feasibility
В Tue, 16 Jan 2024 05:49:01 +
Rolf Turner пишет:
> The problem is persistent/repeatable. I don't believe that there is
> any faulty connection.
One of the things done by R CMD check --as-cran at this point is
sending a HEAD request to every Web link mentioned in the package
documentation and DESCRIPTION. One of the hosts may be slow to respond,
either by accident or due to misguided anti-robot countermeasures.
(Most website protection systems would say that R CMD check counts as a
robot because there's no human behind it to look at the ads.)
Here's what you could try. Unpack your built source package. If you
have a fresh .Rcheck directory from an R CMD check, use
YOURPACKAGE.Rcheck/00_pkg_src/YOURPACKAGE. Then profile the check
function, using the subdirectory from the source package archive as the
argument:
Rprof(); tools:::.check_package_CRAN_incoming(dir); Rprof('NULL')
Does any one function stand out in the subsequent summaryRprof()
output? For me, it's readRDS (not very helpful), but by reading
Rprof.out I can see that it's used by CRAN_package_db and
CRAN_archive_db to download web/packages/packages.rds and
src/contrib/Meta/archive.rds from the chosen CRAN mirror, which for me
takes a few seconds for both files.
Do you have a CRAN mirror set up in ~/.Rprofile? It could be having a
slow day.
--
Best regards,
Ivan
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] checking CRAN incoming feasibility
On Tue, 16 Jan 2024 16:24:59 +1100 Hugh Parsonage wrote: > > Surely the software just has to check > that there is web connection to a CRAN mirror. > > Nope! The full code is in tools:::.check_package_CRAN_incoming (the > body of which filled up my entire console), but to name a few checks > it has to do: check that the name of the package is not the same as > any other, including archived packages (which means that it has to > download the package metadata), make sure the licence is ok, see if > the version number is ok. 10 minutes is quite a lot though. I suspect > the initial connection may have been faulty. Well, it may not have been 10 minutes, but it was at least 5. The problem is persistent/repeatable. I don't believe that there is any faulty connection. Thanks for the insight. cheers, Rolf Turner -- Honorary Research Fellow Department of Statistics University of Auckland Stats. Dep't. (secretaries) phone: +64-9-373-7599 ext. 89622 Home phone: +64-9-480-4619 __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] checking CRAN incoming feasibility
> Surely the software just has to check that there is web connection to a CRAN mirror. Nope! The full code is in tools:::.check_package_CRAN_incoming (the body of which filled up my entire console), but to name a few checks it has to do: check that the name of the package is not the same as any other, including archived packages (which means that it has to download the package metadata), make sure the licence is ok, see if the version number is ok. 10 minutes is quite a lot though. I suspect the initial connection may have been faulty. On Tue, 16 Jan 2024 at 16:15, Rolf Turner wrote: > > > This post essentially amounts to idle curiosity. I don't really expect > that anything can be done about the problem that I perceive. > > When I check a package using --as-cran, the code spits out a line > > checking CRAN incoming feasibility ... > > and then disappears into a black hole for what seems an eternity (5 or > 10 minutes). > > Why does this step take so long? Surely the software just has to check > that there is web connection to a CRAN mirror. I would have thought > that this would be executed virtually instantaneously. > > cheers, > > Rolf Turner > > -- > Honorary Research Fellow > Department of Statistics > University of Auckland > Stats. Dep't. (secretaries) phone: > +64-9-373-7599 ext. 89622 > Home phone: +64-9-480-4619 > > __ > R-package-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
[R-pkg-devel] checking CRAN incoming feasibility
This post essentially amounts to idle curiosity. I don't really expect that anything can be done about the problem that I perceive. When I check a package using --as-cran, the code spits out a line checking CRAN incoming feasibility ... and then disappears into a black hole for what seems an eternity (5 or 10 minutes). Why does this step take so long? Surely the software just has to check that there is web connection to a CRAN mirror. I would have thought that this would be executed virtually instantaneously. cheers, Rolf Turner -- Honorary Research Fellow Department of Statistics University of Auckland Stats. Dep't. (secretaries) phone: +64-9-373-7599 ext. 89622 Home phone: +64-9-480-4619 __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
