Skip to content
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

Automate the sync from genesis test #3490

Open
rootulp opened this issue May 16, 2024 · 0 comments
Open

Automate the sync from genesis test #3490

rootulp opened this issue May 16, 2024 · 0 comments
Labels
testing items that are strictly related to adding or extending test coverage WS: Maintenance 🔧 includes bugs, refactors, flakes, and tech debt etc

Comments

@rootulp
Copy link
Collaborator

rootulp commented May 16, 2024

Context

#2414 proposed two tests and this issue is focused on just one of them:

Create a significantly longer test that syncs mainnet from scratch using a block data archive node.

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.

@rootulp rootulp added testing items that are strictly related to adding or extending test coverage WS: Maintenance 🔧 includes bugs, refactors, flakes, and tech debt etc needs:triage labels May 16, 2024
@rootulp rootulp mentioned this issue May 16, 2024
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing items that are strictly related to adding or extending test coverage WS: Maintenance 🔧 includes bugs, refactors, flakes, and tech debt etc
Projects
None yet
Development

No branches or pull requests

2 participants