-
Notifications
You must be signed in to change notification settings - Fork 113
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
change(ci): Generate mainnet checkpoints in CI #6550
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #6550 +/- ##
==========================================
- Coverage 77.96% 77.89% -0.07%
==========================================
Files 307 307
Lines 40261 40273 +12
==========================================
- Hits 31388 31372 -16
- Misses 8873 8901 +28 |
d78be65
to
75f342f
Compare
b1e8361
to
bb18be3
Compare
This works locally for me, using the same There have been some weird issues where there's no I've just pushed a workaround. |
This is really strange - the test harness works locally, but in Docker + Google Cloud,
|
75f342f
to
838a98d
Compare
3a01761
to
81d50a3
Compare
When I run
(usage output should be here) https://github.com/ZcashFoundation/zebra/actions/runs/4781308585/jobs/8500061799#step:8:179 It seems like there's something wrong with the |
1a50ebb
to
c311186
Compare
@Mergifyio refresh |
✅ Pull request refreshed |
Anyone can re-approve this PR, I just rebased it after PR #6516 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.
Re-approving
Motivation
In #6367 we want to generate checkpoints in CI. This is the mainnet CI and Rust test harness part of that ticket.
Complex Code or Requirements
This is just test code.
Solution
CI workflow:
Rust test harness:
Docker test harness:
zebra-checkpoints binary:
Logging:
Related changes:
And a bunch of minor fixes.
Review
This is a routine CI change.
Reviewer Checklist
Follow Up Work
Next PR: