You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix random failure in TestWebsocketNetworkPrioLimit (#2509)
The peers array is modified when adding/removing entries from it. When that does happen, we increase the peersChangeCounter, so that the broadcast method would know that it's peers list need to be refreshed.
The said update was missing from prioTracker.setPriority, which was causing the issue.
t.Errorf("NetA had the following two peers priorities : [0]:%s=%d [1]:%s=%d", netA.peers[0].rootURL, netA.peers[0].prioWeight, netA.peers[1].rootURL, netA.peers[1].prioWeight)
1190
+
t.Errorf("first peer before broadcasting was %s", firstPeer.rootURL)
1191
+
}
1175
1192
}
1176
1193
1177
1194
// Create many idle connections, to see if we have excessive CPU utilization.
0 commit comments