-
Notifications
You must be signed in to change notification settings - Fork 11
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
test: fix broadcast randomly failing test #1735
base: master
Are you sure you want to change the base?
Conversation
aac282d
to
ffa088d
Compare
Can there be an explanation of why the tests fail using the registered global name? I would try to avoid making the source code more complex simply for tests to pass |
I believe the problem was that the mocking library was having problems unloading the mocks on shared processes and if two tests mock their functionality, sometimes the wrong mocks are used and the tests fail |
Tests should run synchronously for correct mocking and unmocking of the modules, if this is not the case we should figure out a different way to test this module/server (which is working correctly) without having to change it. If it's not possible let's get rid of these tests |
There were different problems that occurred. The problem with the mocking was, that for some runs, where were no As for the registered global name - the problem is, that the Broadcaster using the registered global name is internally using I get that changing such an integral part of the code, such as the Broadcaster is worrying, so if you are wary, we could just leave the test commented for now (but I would still suggest that we try to make future genservers more flexible with regards to global states). |
No description provided.