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

evo-lua / evo-runtime

All-in one Lua runtime based on LuaJIT and libuv

https://evo-lua.github.io

Mozilla Public License 2.0

10 stars 1 forks source link

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

Closed Duckwhale closed 4 months ago

Duckwhale commented 4 months ago

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).