Description
I had a ros session running with a perfectly synchronized clock which I had running for over a week. I started it 2023-10-24.
On Sunday 2023-10-29 early in the morning at 03:00AM the time was set back to 02:00AM as part of the bi-yearly DayLightSavingTime in Germany.
My ReactOS session did miss that switch, and since then is running 1 hour in the future (it displays 12:52 now, although in the real world it is just 11:52).
I left it running for 2 more days to allow our timesvc to kick in, but it didn't correct that glitch even after 2 full days.
I don't think we can learn a lot from my log though:
0.4.15-dev-6788-gd831bc4_DaylightSavingMissed_LogSeemsUselessToMe.log.7z
It was a GCC8.4.0 RosBEWin2.2.2 dbg-build.
Attachments
Issue Links
- blocks
-
CORE-13001 Cannot assign the server time synchronization.
- Resolved
- relates to
-
CORE-19290 Internet Time tab 'Update Now' sets time 1 hour early when Daylight Time is in effect
- Resolved