Closed yurivict closed 8 months ago
Hi there! What timezone are you in? If the machine you ran this from isn't in the same timezone, then can you tell us what timezone the machine is in?
PST
This test will fail on any machine that isn't UTC
To be precise: The hardware clock is in UTC, the user-level timezone is PST.
yes
Maybe you can consider to adjust this case so that it wouldn't assume UTC.
Maybe PR welcome 😃
To be precise: The hardware clock is in UTC, the user-level timezone is PST.
time(nullptr) should return an epoch time based around UTC. It is not, iirc, so this is why this is happening. Are you sure the BIOS clock is correctly set to UTC?
Yes, the BIOS time is in UTC, and time(nullptr)
matches what Internet says the UTC time is.
I feel maybe it's something we should look at rewriting. Whilst it may work for those that live in the UK (like myself), the test fails for people like @Mishura4 as they live in the US.
I'm assuming the user-level timezone is the reason ts_not_null doesn't work, as my mac's VM saw the same issue when the VM decided to set the clock to PST instead of GMT.
awaiting #1080 results, will look to rewrite timestamp test afterwards.
Closed #1080 due to no progress, will look to do this in the next coming days.
A fix for this has now been merged!
Describe the bug
To Reproduce Regular build + test.
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
System Details: