Thanks Tim, I just managed to fix the bug and will prepare a new submission
to CRAN in the upcoming days.
On Wed, 6 Dec 2023 at 11:13, Tim Taylor
wrote:
> This is just a punt from a quick glance at your tests. Try using the
> following on your local build to ensure it's not a time zone issue
>
This is just a punt from a quick glance at your tests. Try using the following
on your local build to ensure it's not a time zone issue
`TZ=NZ R CMD check --as-cran`
`Apologies if this is just noise but whenever I've had issues with datetimes
and mac tests this is the first thing I check.`
`Ti
Sorry, I now see that this may actually be a timezone specific issue which
I can now reproduce in Windows by changing the timezone of the timeseries
to "Pacific/Auckland".
This would indicate that macos-arm64 CRAN machines are based in a different
timezone than the other machines, not the arm64 OS
Hello,
What is the recommended way to create a virtual machine or cloud based R
environment for debugging R package issues specific to OS macos-arm64?
Details:
CRAN results show macos-arm64 specific problems for my package:
https://cran.r-project.org/web/checks/check_results_GGIR.html. I am able
