-
Notifications
You must be signed in to change notification settings - Fork 335
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
Improve CI build/test perf #1113
Conversation
* Use SHA-256 for internal proving tests (2x faster than poseidon) * Avoid hanging cargo-risczero tests waiting on stdin * Avoid building `risc0-zkvm` twice with and without the "prove" feature
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
- run: cargo test -p risc0-r0vm -F $FEATURE -F disable-dev-mode | ||
- run: cargo test -p risc0-zkvm -F $FEATURE -F fault-proof -F prove |
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.
NICE! I feel like we should have caught something like this during code review. I'll try my best to be aware of something like this in the future
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.
By "Something like this", I meant this hunk and the previous one
* Use SHA-256 for internal proving tests (2x faster than poseidon) * Avoid hanging cargo-risczero tests waiting on stdin * Avoid building `risc0-zkvm` twice with and without the "prove" feature
* Use SHA-256 for internal proving tests (2x faster than poseidon) * Avoid hanging cargo-risczero tests waiting on stdin * Avoid building `risc0-zkvm` twice with and without the "prove" feature
risc0-zkvm
twice with and without the "prove" feature