-
Notifications
You must be signed in to change notification settings - Fork 11.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve validator shutdown test #8600
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems reasonable!
assert!(!v.is_running()); | ||
} else { | ||
assert!(v.is_running()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit, can you add a message to the asserts to identify each validator, in case it fails, to help track down what happened?
crates/sui-swarm/src/memory/node.rs
Outdated
.map(|c| c.is_alive()) | ||
.unwrap_or(false) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: map_or_else
?
.map(|c| c.is_alive()) | |
.unwrap_or(false) | |
.map_or(false, |c| c.is_alive()) |
f2fab47
to
4816929
Compare
Instead of expecting a simple panic, we check that a validator that no longer supports the current protocol version shuts itself down.