Generate stateful disks containing lightwalletd-supporting zebra-state cache #3545
Labels
A-devops
Area: Pipelines, CI/CD and Dockerfiles
A-infrastructure
Area: Infrastructure changes
lightwalletd
any work associated with lightwalletd
Motivation
We currently regenerate disk images with
zebra-state
synced up to Sapling activation for use in oursync_past_mandatory_checkpoint
test, so that we don't have to spend hours syncingzebrad
to exercise the relevant code paths of the test. We should do similar for ourlightwalletd
tests, any integration test that requires synced, processed data to be available to azebra-state
/zebrad
instance/test harness, so we don't need to spend extra time syncing.Design
Since this is for general testing and not a particular NU activation height, we should aim for something closer to the most recent NU activation on mainnet.
When syncing, ensure that all build features required for lightwalletd support are enabled, and that the config for
zebrad
has all the lightwalletd functionality enabled to populate the state with the tx index, the compactblock cache, etc.This should run automatically. Currently we regenerate the Sapling checkpoint test state on changes to
zebra-state
format, but that may not be the entire set of changes to trigger on to kick off a new state disk regeneration.https://docs.google.com/document/d/1HrDs0eWZs3s8C5rpwCR5-obCO0nNOXtlG5w4jXD9MJM/edit
Tasks
- [ ] Create a test similar toThis exists as the full sync test to tip.sync_to_mandatory_checkpoint_*
that syncs to a blockheight (NU5 activation?) and stopsFollow-Up Tasks
The text was updated successfully, but these errors were encountered: