1.x: enable TestScheduler with nanosecond periodic scheduling #4884
+147
−70
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 default periodic scheduling code accessed the current worker time as milliseconds which prevents running microsecond and nanosecond scale unit tests with TestScheduler as its internal nanosecond resolution time is always converted, losing precision.
This PR introduces the internal
SchedulePeriodicHelper
class, moves the default scheduling code into a static method and defines aNowNanoSupplier
interface that is now implemented by TestSchedulerWorker to return the current nano time. The defaultWorker.schedulePeriodically
delegates to this static method and given anull
noNanoSupplier
theWorker.now()
is converted to nanoseconds as usual.Related: #4883