This repository has been archived by the owner on Apr 30, 2021. It is now read-only.
MTP-764 DReAM: GlobalClock needs to trigger timers when FastForward() is being called #142
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.
Before, GlobalClock.FastForward() was only adding a time offset to the clock. Now it also triggers the timer callbacks instantaneously when they become due. This change removes the need to use AsyncUtil.Sleep() after a GlobalClock.FastForward() call to get the timers to fire and execute on a background thread.
In addition, there is also a GlobalClock.Suspend() now that makes it possible to stop the clock. This is useful to capture the current time before calling operations that store time internally and then be able to compare the timestamps later.
DO NOT USE THESE METHODS IN PRODUCTION!!!