-
Notifications
You must be signed in to change notification settings - Fork 38
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
Make test-only a CLI argument #521
Conversation
|
||
// If not in test_only mode and running in emulation mode, we'll need to | ||
// initialize the prover state here. | ||
if !prover_config.test_only { |
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.
For #288.
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.
Couldn't be happier with this
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.
Misread, LGTM! Thanks a lot!
It will probably conflict with latest changes on develop (rpc input per block). I think continuations branch should only take continuations related changes since it will probably not be merged to |
It won't be released for a few weeks but I'd rather see it on develop sooner than later given that's its not showing any sign of regression vs develop and conflicts all the time with incoming refactorings from Aatif |
@Nashtare I agree, let's merge it ASAP. What is preventing us to do that today? |
Nothing :D |
Then let's do it 😀 |
Remove the
test_only
conditional compilation feature and make it part of the CLI arguments instead. Technically not related to continuations, but there are enough differences withdevelop
that we might as well merge it here to avoid rebasing later.Includes #288.