Anna Shaleva ef3ec190d0 rpcsrv: allow one-block slippage in TestWSClient_SubscriptionsCompat ... 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>		2024-04-04 11:02:15 +03:00
..
helpers/rpcbroadcaster	*: replace interface{} with any keyword	2023-04-04 13:22:42 +03:00
metrics	services: update logs flush after services shutdown	2024-02-27 15:10:51 +03:00
notary	services: allow some slippage in TestNotary	2024-04-03 18:44:23 +03:00
oracle	*: replace slice.Copy with bytes.Clone	2024-03-05 13:54:10 +03:00
rpcsrv	rpcsrv: allow one-block slippage in TestWSClient_SubscriptionsCompat	2024-04-04 11:02:15 +03:00
stateroot	services: update logs flush after services shutdown	2024-02-27 15:10:51 +03:00