Fix time-machine lib >=3.0.0 supporting changes #60939
Merged
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.
Closes #58470
Fix tests broken by time-machine 3.0+ upgrade
The new
time-machine3.0 removed automatic mocking oftime.monotonic()andtime.monotonic_ns.Also the dateutil support is optional , one can use it as
time-machine[dateutil], we need dateutil as used inRefer below change log of time-machine from 3.0.0 and beyond:
https://time-machine.readthedocs.io/en/latest/changelog.htmlChanges
time-machine[dateutil]to >=3.0.0time.monotonicwithunittest.mock.patchwhere needed as the support is deprecated from 3.0.0 and beyond.monotonic time kept ticking after the time was freezed with time-machine.
time_machine.coordinates.shift()totime_machine.shift()