Ensure now() is always updated in TestScheduler.advanceTo/By#308
Merged
benjchristensen merged 1 commit intoReactiveX:masterfrom Jul 22, 2013
Merged
Ensure now() is always updated in TestScheduler.advanceTo/By#308benjchristensen merged 1 commit intoReactiveX:masterfrom
benjchristensen merged 1 commit intoReactiveX:masterfrom
Conversation
|
RxJava-pull-requests #184 SUCCESS |
Member
|
Makes sense to me, thanks @NorthNick |
benjchristensen
added a commit
that referenced
this pull request
Jul 22, 2013
Ensure now() is always updated in TestScheduler.advanceTo/By
rickbw
pushed a commit
to rickbw/RxJava
that referenced
this pull request
Jan 9, 2014
Ensure now() is always updated in TestScheduler.advanceTo/By
jihoonson
pushed a commit
to jihoonson/RxJava
that referenced
this pull request
Mar 6, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 TestScheduler advanceTimeTo() and advanceTimeBy() methods only update now() correctly if there is a scheduled event in the work queue after the target time. If the queue is empty, now() is not updated at all. If it has no items after the target time, then now() is updated to the time of the last event on the queue.
The pull request ensures now() is always updated to the target time. There is no check to make sure time always moves forwards, but then that check is not in the current implementation either.