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

Fix an issue with perpetually-running timer tests that manifests when another test attempts to use the event loop #534

Merged
merged 1 commit into from
Feb 23, 2024

Conversation

rdw-software
Copy link
Member

@rdw-software rdw-software commented Feb 23, 2024

This wasn't a problem before, but the ticker is never stopped and so the event loop may keep running if it hasn't been explicitly stopped by the other test. The timer API definitely needs some work, but for now this band-aid should help a little bit.

That's why the CI gets stuck on #533 - the new test expects the event loop to fall through, which it can't (due to the tickers).

This wasn't a problem before, but the ticker is never stopped and so the event loop may keep running if it hasn't been explicitly stopped by the other test. The timer API definitely needs some work, but for now this band-aid should help a little bit.
@rdw-software rdw-software merged commit b041030 into main Feb 23, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant