ci: add mainnet blocks in integration tests #147
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Ignacio Hagopian <jsign.uy@gmail.com>
Signed-off-by: Ignacio Hagopian <jsign.uy@gmail.com>
Signed-off-by: Ignacio Hagopian <jsign.uy@gmail.com>
Signed-off-by: Ignacio Hagopian <jsign.uy@gmail.com>
Signed-off-by: Ignacio Hagopian <jsign.uy@gmail.com>
jsign
force-pushed
the
jsign-ci-mainnet-blocks
branch
4 times, most recently
from
da988a2 to
0c23968
Compare
jsign
force-pushed
the
jsign-ci-mainnet-blocks
branch
from
0c23968 to
36022e9
Compare
Signed-off-by: Ignacio Hagopian <jsign.uy@gmail.com>
jsign
force-pushed
the
jsign-ci-mainnet-blocks
branch
from
fcb0f21 to
42ac08f
Compare
Signed-off-by: Ignacio Hagopian <jsign.uy@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a CI integration test to execute 15 mainnet blocks.
Currently, in our CI integration tests, we have execution and proving of the
empty_blockEEST fixture, which runs on every PR as probably the fastest way to have full signal all is okay.Usually, in more risky changes, e.g., updates in the
stateless-validatorcrate or zkVM SDK upgrades, I usually run locally a set of 100 mainnet blocks to have more signal that nothing is broken in more real scenarios. I pulled 15 here since the 100 is ~1GiB tared which can make pulling the repo quite annoying -- the current .tar.gz for 15 is around 75MiB.With this PR I'm pulling more confidence into the CI.