Thanks for the quick (detailed) response.
On 1/31/2025 12:23 PM, Martin Maechler wrote:
Kevin R Coombes
on Fri, 31 Jan 2025 11:48:33 -0500 writes:
> Hi,
> I have a package that has been in CRAN for years and is now failing
> checks because some of the output of a test scrip
> Kevin R Coombes
> on Fri, 31 Jan 2025 11:48:33 -0500 writes:
> Hi,
> I have a package that has been in CRAN for years and is now failing
> checks because some of the output of a test script is differing on some
> machines in the fifth or sixth decimal place. I hav
Hi,h
I have a package that has been in CRAN for years and is now failing
checks because some of the output of a test script is differing on some
machines in the fifth or sixth decimal place. I have managed to fix most
of these issues (by using the "digits" argument in calls to "summary" to
hid
On 29.01.2025 20:08, Simon Urbanek wrote:
LluĂs,
the timestamps are generated by the CRAN server when it updates webpage from
the actual check reports so it does not reflect the date/time of the check
itself (neither does the timestamp of the URL as it is often re-generated). So
in short, n
Hi Wolfgang,
On 31 January 2025 at 15:02, Wolfgang Rolke via R-package-devel wrote:
| In the vignette of my package Rgof I create a function written in Rcpp, which
is then passed and executed in some of the routines included in Rgof. The
package passes all the checks on the various platform wit
In the vignette of my package Rgof I create a function written in Rcpp, which
is then passed and executed in some of the routines included in Rgof. The
package passes all the checks on the various platform without errors, warnings
or notes except on atlas and gcc13. There I get an error about no