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
I expect the system time in all tasks to be somewhat correct so that e.g, build systems based on timestamps correctly work locally, or e.g., cert timestamps are okay.
Real Behavior
Looking at the time on VMs started for big_sur_baseos_x_instances, it seems to lag one week behind.
This causes issues with external resources when during downloads certificates from the future are encountered which cannot be validated, see e.g., zeek/zeek#1791.
This currently also causes issues when building a CMake project with a Homebrew-installed cmake: due to a recent release of the Homebrew artifacts the files in that package currently have timestamps like
Due to that such builds are always outdated and try to reconfigure themselves until the build setup is newer than all inputs:
ninja explain: output build.ninja older than most recent input /usr/local/Cellar/cmake/3.21.3/share/cmake/Modules/BasicConfigVersion-SameMajorVersion.cmake.in (1631582225469588131 vs 1632156232000000000)
There are probably more scenarios affected by this.
Related Info
Website issue
Task issue
OS: macOS
The text was updated successfully, but these errors were encountered:
Expected Behavior
I expect the system time in all tasks to be somewhat correct so that e.g, build systems based on timestamps correctly work locally, or e.g., cert timestamps are okay.
Real Behavior
Looking at the time on VMs started for
big_sur_base
os_x_instance
s, it seems to lag one week behind.This causes issues with external resources when during downloads certificates from the future are encountered which cannot be validated, see e.g., zeek/zeek#1791.
This currently also causes issues when building a CMake project with a Homebrew-installed
cmake
: due to a recent release of the Homebrew artifacts the files in that package currently have timestamps likeThe build setup generated by CMake is timestamped with the local time:
Due to that such builds are always outdated and try to reconfigure themselves until the build setup is newer than all inputs:
There are probably more scenarios affected by this.
Related Info
The text was updated successfully, but these errors were encountered: