-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
chore: Add CI checks for prover
directory
#201
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #201 +/- ##
==========================================
- Coverage 32.75% 32.70% -0.06%
==========================================
Files 536 536
Lines 28133 28135 +2
==========================================
- Hits 9216 9201 -15
- Misses 18917 18934 +17
☔ View full report in Codecov by Sentry. |
I thought we'd be renaming components as well between FRI and non-FRI. That said, it's not a blocker. I'd prefer if we "context"-ed all errors so we have a good trace. I know it's not part of this work, but would be great to be done alongside. This said, I'm a big fan of the work done, thanks for the effort! |
What ❔
prover
directoryprover
directoryprover/prover
andprover/setup_key_generator_and_server
compilable without a GPU.ci_run
script (before, prover unit tests weren't being run at all)zk
tool to includezk lint prover
andzk test prover
Why ❔
Following good practices & reducing technical debt.
Checklist
zk fmt
andzk lint
.