David Wang f499c6b9ec Test: wait for network changes in TestNetworkDBNodeJoinLeaveIteration ...

In network node change test, the expected behavior is focused on how many nodes
left in networkDB, besides timing issues, things would also go tricky for a
leave-then-join sequence, if the check (counting the nodes) happened before the
first "leave" event, then the testcase actually miss its target and report PASS
without verifying its final result; if the check happened after the 'leave' event,
but before the 'join' event, the test would report FAIL unnecessary;

This code change would check both the db changes and the node count, it would
report PASS only when networkdb has indeed changed and the node count is expected.

Signed-off-by: David Wang <00107082@163.com>

2022-07-21 22:56:58 +08:00

..

broadcast.go

Optimize networkDB queue

2018-07-02 16:59:45 -07:00

cluster.go

libnetwork/networkdb: remove some redundant fmt.Sprintf()'s

2022-02-15 12:56:23 +01:00

delegate.go

Optimize networkDB queue

2018-07-02 16:59:45 -07:00

event_delegate.go

Avoid delay on node rejoin, avoid useless witness

2018-01-23 16:21:18 -08:00

message.go

NetworkDB allow setting PacketSize

2017-07-26 13:44:33 -07:00

networkdb_test.go

Test: wait for network changes in TestNetworkDBNodeJoinLeaveIteration

2022-07-21 22:56:58 +08:00

networkdb.go

gofmt GoDoc comments with go1.19

2022-07-08 19:56:23 +02:00

networkdb.pb.go

Update to Go 1.17.0, and gofmt with Go 1.17

2021-08-24 23:33:27 +02:00

networkdb.proto

Spelling fixes

2018-07-12 12:54:44 -07:00

networkdbdiagnostic.go

Fix libnetwork imports

2021-06-01 21:51:23 +00:00

nodemgmt.go

Cleanup node management logic

2017-12-13 09:40:38 -08:00

watch.go

Fix leak of handleTableEvents

2017-05-31 11:04:19 -07:00