Automate the sync from genesis test #3490
Labels
testing
items that are strictly related to adding or extending test coverage
WS: Maintenance 🔧
includes bugs, refactors, flakes, and tech debt etc
Context
#2414 proposed two tests and this issue is focused on just one of them:
Problem
We currently support a feature called "single binary syncs" whereby we commit to supporting the ability to run one binary and sync from genesis to the tip of the chain. However, we don't have a test that verifies this feature and we've already introduced regressions to the v1.x line (e.g. ibc-go bump released in celestia-app v1.8.0) that break the feature.
Proposal
Create an automated way to test that the latest release or current
main
is able to sync from genesis.Note: we currently test this manually via
mainnet.sh
but that takes over a month so this test likely needs to speed up the time to sync. My hunch is that block sync takes a ton of time so we may be able to speed this up a lot by creating a snapshot of a node with all the blocks downloaded already. Then in a test we can spin up a node using the image and execute the latest binary against all the downloaded blocks.The text was updated successfully, but these errors were encountered: