-
Notifications
You must be signed in to change notification settings - Fork 79
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
Failing Windows subscriptions test #2956
Comments
@AliceInHunterland, this issue is not related to #3340, it's a separate problem because here we start a full separate RPC server. I had a thought that the reason for this test failure was connected with the fact that RPC server doesn't wait for the end of execution of |
Close exit channel on exit, wait more for the test to finish. Ref. #2956. Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
Close #2956. The failure reason is similar to the one described in #3396 for TestNotary: Blockchain's notificationDispatcher is listening to block events from storeBlock via separate channel. By the moment single block addition is finished, notification may or may not be properly handled by notificationDispatcher, especially given the fact that our runners are slow. As a result, assert.Eventually with 1-second awaiting period may fail. This issue is solved by adding one more block, because the second AddBlock finishes only when it sends block addition event to notificationDispatcher loop, which means that the previous event was handled. Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
Close #2956. The failure reason is similar to the one described in #3396 for TestNotary: Blockchain's notificationDispatcher is listening to block events from storeBlock via separate channel. By the moment single block addition is finished, notification may or may not be properly handled by notificationDispatcher, especially given the fact that our runners are slow. As a result, assert.Eventually with 1-second awaiting period may fail. This issue is solved by adding one more block, because the second AddBlock finishes only when it sends block addition event to notificationDispatcher loop, which means that the previous event was handled. Signed-off-by: Anna Shaleva <shaleva.ann@nspcc.ru>
Not sure whether it's a bug, but these tests were OK several days ago and it's better to be fixed.
The text was updated successfully, but these errors were encountered: