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
We have a good test for chain upgrades, but we should also have an automated test that uses real chain data and see if a new version (PR) will cause app hash errors when one node in a network uses a new version.
Some notes:
Reuse (maybe pull out into a reusable workflow) the "Export EmpowerChain Genesis" from chain_upgrade-test.yml
Start up a small network of 3-5 nodes or something
Upgrade one node
Run a bunch of simulations (transactions)
See if the upgraded node is still running
Another option to the simulation/transactions is to let an upgraded node start behind and catch up (rerun old transactions).
The text was updated successfully, but these errors were encountered:
We have a good test for chain upgrades, but we should also have an automated test that uses real chain data and see if a new version (PR) will cause app hash errors when one node in a network uses a new version.
Some notes:
Another option to the simulation/transactions is to let an upgraded node start behind and catch up (rerun old transactions).
The text was updated successfully, but these errors were encountered: