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

ci: run a full lightwalletd sync from a close-to-tip zebrad #3926

Closed
gustavovalverde opened this issue Mar 21, 2022 · 3 comments · Fixed by #4268
Closed

ci: run a full lightwalletd sync from a close-to-tip zebrad #3926

gustavovalverde opened this issue Mar 21, 2022 · 3 comments · Fixed by #4268
Assignees
Labels
A-devops Area: Pipelines, CI/CD and Dockerfiles C-enhancement Category: This is an improvement lightwalletd any work associated with lightwalletd

Comments

@gustavovalverde
Copy link
Member

gustavovalverde commented Mar 21, 2022

Motivation

On every PR push, if the zebrad state format hasn’t changed, we want to run a full lightwalletd sync from a close-to-tip zebrad, as a test. This test should take 30 minutes

Designs

Related Work

#3922

@gustavovalverde gustavovalverde added A-devops Area: Pipelines, CI/CD and Dockerfiles C-enhancement Category: This is an improvement S-needs-triage Status: A bug report needs triage P-High 🔥 lightwalletd any work associated with lightwalletd and removed P-High 🔥 labels Mar 21, 2022
@teor2345
Copy link
Contributor

Is this the same as #3511?

@gustavovalverde
Copy link
Member Author

@teor2345 I added #3511 as a dependency. Considering the test must be created (#3511) and then added to the CI (#3926)

@teor2345
Copy link
Contributor

This is a high priority, because it is on the critical path, and blocking other lightwalletd integration tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-devops Area: Pipelines, CI/CD and Dockerfiles C-enhancement Category: This is an improvement lightwalletd any work associated with lightwalletd
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants