We make no guarantees about consistency between RPC calls.
Alternative to 18784
We make no guarantees about consistency between RPC calls.
Alternative to 18784
We make no guarantees about consistency between RPC calls.
review ACK 778cd0d88d8d6dd22d7f0fb740f3ca3dbb2280a1
ACK 778cd0d88d8d6dd22d7f0fb740f3ca3dbb2280a1 after reading discussion on 18784, code review, ran test
138 | - peer_info_after_ping = self.nodes[0].getpeerinfo() 139 | - for before, after in zip(peer_info, peer_info_after_ping): 140 | + peer_info_after = self.nodes[0].getpeerinfo() 141 | + for before, after in zip(peer_info_before, peer_info_after): 142 | assert_greater_than_or_equal(after['bytesrecv_per_msg'].get('pong', 0), before['bytesrecv_per_msg'].get('pong', 0) + 32) 143 | assert_greater_than_or_equal(after['bytessent_per_msg'].get('ping', 0), before['bytessent_per_msg'].get('ping', 0) + 32)
This still assumes they are synchronised/consistent. the assert should be replaced by a wait_until. See #20299