Actually, it looks like R CMD check has _intended_ to just skip in the
case the website is misbehaving:
https://github.com/r-devel/r-svn/blob/3578a3f858136a8abcd2f708f38a8dff6225ec42/src/library/tools/R/check.R#L549-L552
My guess is this test should be improved, currently we get (logical)
NA if t
Does all this mean that the check is not handling its own errors?
On Sat, 8 Feb 2025 at 8:28 AM, Henrik Bengtsson
wrote:
> > It has to have the "datetime" entry. If you can't fix your network you
> can skip that test with
> >
> > _R_CHECK_FUTURE_FILE_TIMESTAMPS_=FALSE
>
> I'm quite sure that is
> It has to have the "datetime" entry. If you can't fix your network you can
> skip that test with
>
> _R_CHECK_FUTURE_FILE_TIMESTAMPS_=FALSE
I'm quite sure that is overridden 'R CMD check' when using the
--as-cran flag. The workaround that I have found is to set environment
variable:
_R_CHECK_S
Josiah,
that test tests the accuracy of the system clock by querying
https://worldtimeapi.org/api/timezone/etc/UTC so my guess would be that you
have either network or proxy issues which cause that request to fail by
providing garbage instead of the actual response.
The call to test yourself
Thanks, Duncan!
It is produced before preparing the tarball. It’s just a way to automate
defining many 100ish functions that have the same structure. l run the
script manually when I want to update definitions.
There is not any auto-magical process that creates a file before the build
or instal
One question is when that file is produced. Do you produce it before
preparing the tarball, or is it produced as part of the installation
process?
Duncan Murdoch
On 2025-02-04 6:27 p.m., Josiah Parry wrote:
The file was written using writeLines() but it is just a normal R script
with normal
That was clear to me, and changes nothing about my comments.
On February 4, 2025 3:27:34 PM PST, Josiah Parry wrote:
>The file was written using writeLines() but it is just a normal R script
>with normal function definitions and is included in the R/ directory. The
>source code is just programmat
The file was written using writeLines() but it is just a normal R script
with normal function definitions and is included in the R/ directory. The
source code is just programmatically generated.
On Tue, Feb 4, 2025 at 14:54 Jeff Newmiller
wrote:
> Packages are supposed to work when mounted in a
Packages are supposed to work when mounted in a read-only filesystem... using
writeLines seems like a very bad idea since you can't assume the package
install is writeable when it is run, and running code from tmp is a security
hole.
If you absolutely cannot think of a way around running code f
