You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 15, 2024. It is now read-only.
I have been working on my anytime package and noticed something strange when running check_for_cran(). This is likely related to TZ and timezone settings. I consistently get the 'basic' Fedora and Ubuntu setups to fail, while Debian SAN/UBSAN passes.
It is of course entirely possible that I am doing something wrong or silly with the TZ detection. But it a) passes for me under all settings at home (using "America/Chicago") and b) also passes in Docker container when I use not TZ setting or when I use TZ="UTC". There is a known issue with Europe/London but that is different.
I worked around the issue by limiting tests when in release -- my scheme is using a.b.c as a release version whereas a.b.c.d is a development version in which all tests runs. So when reproducing make sure DESCRIPTION has an added digit for the version. To recap:
This has four passes for 0.3.4 because fewer tests run, for 0.3.4.1 all run and the two failure occur on
I have been working on my anytime package and noticed something strange when running
check_for_cran()
. This is likely related toTZ
and timezone settings. I consistently get the 'basic' Fedora and Ubuntu setups to fail, while Debian SAN/UBSAN passes.It is of course entirely possible that I am doing something wrong or silly with the TZ detection. But it a) passes for me under all settings at home (using "America/Chicago") and b) also passes in Docker container when I use not
TZ
setting or when I useTZ="UTC"
. There is a known issue withEurope/London
but that is different.I worked around the issue by limiting tests when in release -- my scheme is using a.b.c as a release version whereas a.b.c.d is a development version in which all tests runs. So when reproducing make sure
DESCRIPTION
has an added digit for the version. To recap:This has four passes for 0.3.4 because fewer tests run, for 0.3.4.1 all run and the two failure occur on
Platform: Ubuntu Linux 16.04 LTS, R-release, GCC
Platform: Fedora Linux, R-devel, clang, gfortran
Let me if / how I can help.
The text was updated successfully, but these errors were encountered: