Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor(observeOn-spec): use a scheduler instead of setInterval #2252

Merged
merged 1 commit into from
Jan 5, 2017
Merged

refactor(observeOn-spec): use a scheduler instead of setInterval #2252

merged 1 commit into from
Jan 5, 2017

Conversation

benlesh
Copy link
Member

@benlesh benlesh commented Jan 5, 2017

The idea here is to promote a more consistent scheduling of each value across multiple browsers. It seems there were some concurrency problems when this test was run in Microsoft Edge. Hopefully this clears it up.

related #2244

The idea here is to promote a more consistent scheduling of each value across multiple browsers. It seems there were some concurrency problems when this test was run in Microsoft Edge. Hopefully this clears it up.

related #2244
@coveralls
Copy link

coveralls commented Jan 5, 2017

Coverage Status

Coverage remained the same at 97.696% when pulling 8f63ba8 on blesh:fix-edge-tests into 79afcd3 on ReactiveX:master.

@benlesh benlesh merged commit 7e45ce1 into ReactiveX:master Jan 5, 2017
@lock
Copy link

lock bot commented Jun 6, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants