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

Re-enable post-Sapling mainnet sync tests #1529

Merged
merged 3 commits into from
Dec 16, 2020
Merged

Re-enable post-Sapling mainnet sync tests #1529

merged 3 commits into from
Dec 16, 2020

Conversation

dconnolly
Copy link
Contributor

@dconnolly dconnolly commented Dec 16, 2020

Motivation

We disabled our post-Sapling stateful sync tests when the state format changed and required a re-caching of state.

Solution

This re-enables the mainnet test with the newly synced v4 state disk, when testnet is also re-synced I'll enable that in another PR.

Review

Not urgent, will test with a manual trigger of the 'Test' workflow.

Related Issues

Follow Up Work

Re-enable the testnet variant when the re-sync disk is ready. @dconnolly

@teor2345
Copy link
Contributor

This re-enables the mainnet test with the newly synced v3 state disk,

I think we're at database format version 4 right now?
https://github.com/ZcashFoundation/zebra/blob/main/zebra-state/src/constants.rs#L14

Copy link
Contributor

@teor2345 teor2345 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, I just want to double-check a few details.

@dconnolly
Copy link
Contributor Author

This re-enables the mainnet test with the newly synced v3 state disk,

I think we're at database format version 4 right now?
https://github.com/ZcashFoundation/zebra/blob/main/zebra-state/src/constants.rs#L14

You're right! 👀

Copy link
Contributor

@teor2345 teor2345 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@teor2345
Copy link
Contributor

(The macOS failure is a GitHub PR git ref error.)

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