Fix runOnlyPendingTimers for setTimeout inside setImmediate#4608
Merged
Conversation
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Nested calls to timer mocks (
setTimeout/setInterval) insidesetImmediatewere unreliable withjest.runOnlyPendingTimers.To fix this, we need to store the timers object before executing immediates – simply clone timers (assigning will hold the reference) at the very beginning of
jest.runOnlyPendingTimersso we're sure we're going to run only pending timers :D. Otherwise the timers object gets populated with timers that should not be there yet.Fixes #3048
Test plan
Updated the existing test to support currently failing case