Skip to content

Add chaos testing #111

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

Closed
wants to merge 1 commit into from
Closed

Add chaos testing #111

wants to merge 1 commit into from

Conversation

ferranbt
Copy link
Collaborator

This is still a draft since the setup is not that good yet.

The idea is that we can use a setup to deploy an Op-stack network (with Rollup-boost) and then create a unit test to deploy a reth builder with a proxy in front using the same utilities we use for integration tests.

Once that is done, we can randomly add delays and drop connections from the proxy to simulate chaos. Our success criteria is that even in this scenario, the liveness of the chain is not affected (there is a block every n seconds).

To deploy this setup you have to:

Run this branch for the legacy op-stack docker-compose setup:

$ make devnet-up

Run rollup-boost:

$ cargo run -- --l2-url http://localhost:8551 --builder-url http://localhost:4444 --l2-jwt-token 688f5d737bad920bdfb2fc2f488d6b6209eebda1dae949a8de91398d932c517a --builder-jwt-token 688f5d737bad920bdfb2fc2f488d6b6209eebda1dae949a8de91398d932c517a

Run the unit test:

$ cargo test --features integration -- integration::integration_test::tests::test_integration_chaos --show-output --nocapture

Note that in the current unit test the genesis path is hardcoded to my computer. You would have to change that to test this.

My current thoughts:

  • We should not use the docker-compose setup since it is a legacy system though I am not a fan of Kurtosis.
  • The setup gets (way) more complicated if we have first to create a local Rollup-boost docker image and then run Kurtosis.

@0xKitsune
Copy link
Collaborator

Closing for now due to inactivity. If this should be revisited, feel free to open a new issue/PR.

@0xKitsune 0xKitsune closed this May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants