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
After resetting m.t.s.c, the node count should be exactly 50 (unless somebody is running extra validator nodes attached to m.t.s.c -- possible but unlikely at this point).
After adding 17d927a, it shows a node count of 80 or other numbers not 50.
It's possible we have some kind of crdt table issue.
I suspect it is but we don't have a nice way to detect if/when this happens. I think we could add a --strict flag to bench-tps that turns this expression [1] from a < to !=, then enable --strict on the internal testnets. If it doesn't blow up then this issue can be closed
After resetting m.t.s.c, the node count should be exactly 50 (unless somebody is running extra validator nodes attached to m.t.s.c -- possible but unlikely at this point).
After adding 17d927a, it shows a node count of 80 or other numbers not 50.
It's possible we have some kind of crdt table issue.
STR: Look at the output from the latest build at https://buildkite.com/solana-labs/testnet-deploy
cc: #693
cc: #695
The text was updated successfully, but these errors were encountered: