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
Gut does not stop internal timer after callback. #450
Comments
I made a test on my project https://github.com/theludovyc/Rakugo/blob/a620421257fe4b64e8b084cd26e22b6e5ffb6b9f/Test/TestParser/TestAsk/TestAsk.gd#L12 It passed some times, but often failed. yield_to never wait time in parameters, even if I set it to 5s. Always instant. But if I wait the previous signal (like there https://github.com/theludovyc/Rakugo/blob/a620421257fe4b64e8b084cd26e22b6e5ffb6b9f/Test/TestParser/TestSay/TestSay.gd#L12), it never failed. Can this bug cause that ? |
It's possible. You can try the workarounds below to see if it makes the test consistent. I looked back at the code to try and figure out what "complex setups" means, and I can't think of a valid example of when this will happen. I'm sure this is a bug, probably, but I don't know what I found when I made this issue. You can stop the timer after each test so that the time remaining does not leak into the next test.
If you have multiple calls to |
Fixed in |
Thank you 😊 |
In some complex setups GUT it is possible to cause GUT to yield for less time than it is supposed to.
_yielding_callback
should call_yield_timer.stop()
.The text was updated successfully, but these errors were encountered: