use different timezones to run CI tests #1259
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The test fails when it runs at midnight or, in general, when a time difference causes changes in dates for UTC and non-UTC time zones.
Some tests expect the local timezone to be picked resulting in a different expectation than the actual result. The result of the
search_dates
method picks UTC when nothing is provided in the absence of date & time.Additionally, I reckon the issue was introduced in #1111, where
datetime.datetime.utcnow().month
was replaced withdatetime.datetime.today().month
.