-
Notifications
You must be signed in to change notification settings - Fork 120
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(sync): only run the lightwalletd
full sync on the main
branch
#5393
Conversation
Previous behavior: In PR #5164, we made lightwalletd sync all the way to the tip in its full sync test. This increases that test's time from 1 hour to 4 hours, which makes the CI we run on each PR change increase from 3 hours to 6 hours. Expected behavior: Run the lightwalletd full sync just on `main` or if a state disk for the actual version is not found. Solution: Add the `github.event_name == 'push' && github.ref_name == 'main'` condition to the `lightwalletd-full-sync` test. Fixes #5316
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Protection rules updated to allow this and other PRs to be merged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Protection rules updated to allow this and other PRs to be merged
This PR disables the requirement for the lwd
full sync job, but we added a patch job for the zebrad
full sync job.
zebra/.github/workflows/continous-integration-docker.patch-always.yml
Lines 18 to 22 in 8646a03
test-full-sync: | |
name: Zebra tip / Run full-sync-to-tip test | |
runs-on: ubuntu-latest | |
steps: | |
- run: 'echo "No build required"' |
Can we choose one way to do it, and make it consistent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about the conditions here, I think we might want to match the full sync job almost exactly?
I'll also push a PR with some more suggestions.
This has been updated accordingly |
I added an "always" patch job, and re-added the branch protection rule. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I think we're good to go here.
Previous behavior
In PR #5164, we made lightwalletd sync all the way to the tip in its full sync test.
This increases that test's time from 1 hour to 4 hours, which makes the CI we run on each PR change increase from 3 hours to 6 hours.
Expected behavior
Run the lightwalletd full sync just on
main
or if a state disk for the actual version is not found.Solution
Add the
github.event_name == 'push' && github.ref_name == 'main'
condition to thelightwalletd-full-sync
test.Fixes #5316
Review
Anyone from the DevOps team
How to test: This job should not run in this PR
Reviewer Checklist
Follow Up Work