-
Notifications
You must be signed in to change notification settings - Fork 4k
test: example upgrade handler and systems test #24182
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
Conversation
|
||
modifications := [][]string{ | ||
{"genesis", "add-genesis-account", v50CLI.AddKey("foo"), "10000000000stake"}, | ||
{"genesis", "add-genesis-account", v50CLI.AddKey("bar"), "10000000000stake"}, | ||
{"genesis", "add-genesis-account", v50CLI.AddKey("baz"), "10000000000stake"}, | ||
} |
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.
lets add a comment here:
"typically, SystemUnderTest will create a node with 4 validators. In the legacy setup, we create run a single validator network. This means we need to add 3 more accounts in order to make further account additions map to the same account number in state."
|
||
t.Log("waiting for upgrade info") | ||
systest.Sut.AwaitUpgradeInfo(t) | ||
systest.Sut.StopChain() | ||
|
||
t.Log("Upgrade height was reached. Upgrading chain") | ||
systest.Sut.SetExecBinary(currentBranchBinary) | ||
systest.Sut.SetTestnetInitializer(currentInitializer) | ||
systest.Sut.StartChain(t) |
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.
can we assert that the correct height was reached? and that the new chain starts at upgradeHeight + 1?
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.
added assertion assert block height
i think |
Closes 24168