-
Notifications
You must be signed in to change notification settings - Fork 226
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
ci job to detect divergence (e.g. multi-node local chain) #3444
Comments
@mhofman you noted lately that you weren't sure about automated techniques for a multi-node chain. This looks pretty interesting, to me. It's different from the way @michaelfig usually does it, but I don't understand some of the motivation for his approach (terraform, ...). cc @warner |
The motivation is that I want to use the same process for CI testing that we actually use to deploy the The Gaia style of testing is reasonable, too, though. Probably some combination of the two will be useful. |
Simple case will be done as part of CI. We don't currently do node restarts, but should be straightforward with Michael's new tools. |
@mhofman Please create new issue for longer term stop/restart multiple validator node test, then close this. |
Done and merged. |
Opened #4557 for a stop/restart based test |
To start a multi-node test chain, we have a
scenario1
, but it involves more infrastructure than I expected (terraform, ansible) and seemed to take more disk space than I expected.gaia
has a docker-compose based approach that is about the size and shape of what I expected. I'd like to try porting this toag-chain-cosmos
.https://github.com/cosmos/gaia/blob/main/docs/gaia-tutorials/installation.md and https://github.com/cosmos/gaia/blob/main/docs/gaia-tutorials/deploy-testnet.md got me a 4 node cosmos network:
The text was updated successfully, but these errors were encountered: