4 ms·
A related too for CI: change the system time to be a time zone that is during your work hours in a different day already than UTC. Really helped getting failure
by ajmurmann 5y ago
A related too for CI: change the system time to be a time zone that is during your work hours in a different day already than UTC. Really helped getting failures earlier than 4pm PST.
- brundolf 5y agoAt my last job we had a wild time-zone bug that only happened with your system location set to Mumbai. I left mine set to that for the rest of my time there.
- cpeterso 5y agoRelated: here's a recent Firefox bug about a test that failed during the daylight saving time change: https://bugzilla.mozilla.org/show_bug.cgi?id=1739847 https://bugzilla.mozilla.org/show_bug.cgi?id=1739847
- scubbo 5y agoCould you consider rephrasing this? It sounds like an interesting observation that I'd love to understand, but I'm genuinely not able to parse it. My best guess is "change the system time to be a timezone for which, during your work hours, the other-timezone is in a different day than UTC is" - but I'm still not sure what effect that would have on CI failures.
- Teknoman117 5y agoI read that as "set your CI to run earlier in your workday so you don't get new error reports at the end of the day." Midnight UTC being 4 pm/16:00 PST.
- ajmurmann 5y agoMaybe an example of the failure this detects helps: when I used to work on Rails apps in the olden days it was easy to call Time.now and get the local time instead of Time.zone.now to get UTC time. This often lead to wrong dates but tests would only fail once it was a new day in UTC land but still the old day in the local time zone. Making the CI machine's system time something Fiji time really helped in getting failures much sooner after changes were pushed.